README.md

Shared React sources

The source of truth for the parts of the React starters that must stay identical: the design tokens, the app shell layout, the UI kit, and the fetch seam the kit calls.

Both templates/web/react-vite and templates/web/react-oauth carry a committed copy of everything here. The Next.js, Angular, Vue and SvelteKit starters carry only the design tokens (index.css) and the fonts. Edit the file in this directory, then run:

npm run sync:shared

npm run validate fails when a copy has drifted, so CI and the pre-commit hook both catch an edit made to a template copy instead of to the source.

Formatting

The copies are byte for byte identical to the source, so a file here has to be stored in the exact form the templates' own format:check expects. One prettier at the repo root, with a .prettierrc.json matching the templates', formats the whole repository including this directory:

npm run format

The pre-commit hook runs npm run format:check, so a file formatted with anything else does not reach a commit. That matters because the root used to declare neither prettier nor a config: prettier resolved no options for this directory and npx was free to pick up whatever version was on the machine. A major behind, and every synced copy failed its template's format:check on files nobody had edited.

Why copies rather than a package or a symlink

seamless-cli copies exactly one template directory into a new project. A template cannot reference anything outside its own directory, because nothing outside it is copied. That rules out importing from a repo-root directory, and a symlink is both fragile across platforms and useless once the template is copied. Publishing the kit to npm would work, but this repository is private and is not published; its shipped artifact is a git tag.

So each template gets a real copy, and the drift check is what keeps the copies honest. The copies carry no generated-file banner on purpose: they are ordinary source in the project a user scaffolds, and a banner pointing at a directory that does not exist in their project would only confuse them.

What is in here

Path	Copied to
index.css	src/index.css
layouts/Layout.tsx	src/layouts/Layout.tsx
components/kit/	src/components/kit/
lib/	src/lib/
fonts/	public/fonts/

fonts/ is the one binary entry, so the sync script compares and copies in buffers rather than as text.

lib/ is here because the kit imports it. useCollection reaches for ../../lib/api, so the two cannot be maintained apart: a change to what apiFetch throws is a change to what the kit has to handle. The two copies were already byte for byte identical before the manifest listed them, with nothing keeping them that way.

sync.json is the manifest the sync script reads. .prettierrc.json matches the one each template ships, so formatting these sources with the template's Prettier produces the same bytes the templates are checked against.

What is deliberately not shared

src/components/Navbar.tsx is per-template. Each starter lists its own routes in the nav, and react-oauth has no beta-access route. The file is also an anchor for code generation: tooling that scaffolds routes on top of a template patches its own nav links in beside the literal { label: "Home", to: "/" }, entry, so the array has to stay written out in each template rather than moving behind an abstraction.