@sushindustries/adam-jurek

0.1.011 views

The whole system in one install: every component, the stylesheet they are built on, and nothing else. Private on purpose - the pieces publish, the bundle does not.

pnpm add @sushindustries/adam-jurek
2 min read
View as Markdown

The whole system in one install. This package re-exports every component in @sushindustries/ui@sushindustries/uiThe components this site is made of. Every one of them is installable on its own - nothing here is site-specific.package and depends on @sushindustries/atoms@sushindustries/atomsThe design tokens and the atomic utilities built on them. One stylesheet, no build step, no framework.package, so one dependency line and one stylesheet import is the entire setup.

The pieces still publish on their own - each component installs through three doors - and this bundle exists for the one consumer that genuinely wants all of it: a project that is being built as an Adam Jurek project from the first commit.

Install

The umbrella publishes to GitHub Packages, so point the scope there once in .npmrc (installing needs a GitHub token with read:packages):

@sushindustries:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=${GH_PACKAGES_TOKEN}
pnpm add @sushindustries/adam-jurek
shell

ui@sushindustries/uiThe components this site is made of. Every one of them is installable on its own - nothing here is site-specific.package and atoms@sushindustries/atomsThe design tokens and the atomic utilities built on them. One stylesheet, no build step, no framework.package arrive with it - the umbrella is exactly those two, wired. Inside the workspace it is "@sushindustries/adam-jurek": "workspace:*".

The one-sentence setup

import { Consent, ScrollSpin, FolderShelf } from "@sushindustries/adam-jurek";
import "@sushindustries/atoms/atoms.css";
ts

The stylesheet stays an explicit import because CSS is not re-exportable - and because knowing where the cascade comes from is worth one line.

The three doors, for everyone else

DoorWhat it isOne-time setup
npmpnpm add @sushindustries/ui @sushindustries/atomsnone
shadcncopy-paste ownership of single components, stylesheet included automatically"registries": { "@adamjurek": "<origin>/r/shadcn/{name}.json" } in components.json
TanStack CLIadd-ons with pinned versions, for tanstack create projectsnone - point --add-ons at /r/registry.json

Every component page on the site prints its own commands for all three, and the shadcn payloads carry the stylesheet as a registry dependency - a copied component arrives styled, not naked.

What does not belong here

Anything. A component that would earn a line of its own in this package belongs in ui@sushindustries/uiThe components this site is made of. Every one of them is installable on its own - nothing here is site-specific.package; a style belongs in atoms@sushindustries/atomsThe design tokens and the atomic utilities built on them. One stylesheet, no build step, no framework.package. The umbrella that starts accumulating its own code is two packages wearing one name.