Skip to content

fix(registry): ship stylesheets as registry:file so shadcn add works - #1050

Open
Agnik47 wants to merge 1 commit into
DavidHDev:mainfrom
Agnik47:feat/fix-shadcn-css-install
Open

fix(registry): ship stylesheets as registry:file so shadcn add works#1050
Agnik47 wants to merge 1 commit into
DavidHDev:mainfrom
Agnik47:feat/fix-shadcn-css-install

Conversation

@Agnik47

@Agnik47 Agnik47 commented Aug 22, 2026

Copy link
Copy Markdown

Closes #1049

Problem

npx shadcn add @react-bits/<Component>-JS-CSS fails with Unexpected token (1:0) right after "Checking registry", at the "Updating files" step.

It isn't specific to Lanyard — every one of the 292 -CSS registry entries is affected. -TW variants ship no stylesheet and were always fine.

The shadcn CLI runs every file it installs through its JavaScript/TypeScript transformer unless the file is typed registry:file. jsrepo.config.ts shipped each component as a whole folder, and a folder can't declare a type per file, so stylesheets went out as registry:component and got parsed as JavaScript. Unexpected token (1:0) is the parser choking on the first character of the CSS.

Fix

Stylesheets are now declared as registry:file, which shadcn copies verbatim. registry:file requires an explicit target, so it is set to @components/<Name>.css — shadcn resolves the @components alias to whatever the user configured in their components.json, which is where the component itself lands, so the component's relative ./<Name>.css import keeps resolving.

Because of the per-file type, variants that actually ship a stylesheet are now listed file by file instead of as a folder. Everything else still ships as a folder, so all -TW entries stay byte-identical.

public/r/ is regenerated (npm run registry:build). That rebuild also picks up ~57 entries whose committed content had drifted from src/ before this PR — those are content-only refreshes, no structural change.

Testing

  • Reproduced first against the live registry with shadcn 4.16.0, 4.17.0 and 4.18.0 — all three fail on Lanyard-JS-CSS, Aurora-JS-CSS and AccordionGallery-JS-CSS, while Aurora-JS-TW installs fine.
  • Re-ran npx shadcn add against the rebuilt registry on all three CLI versions, in both a JS project ("tsx": false) and a TS project ("tsx": true): Lanyard, Aurora, Hyperspeed, AccordionGallery, Magnet, BlurText, ASCIIText (-JS-CSS / -TS-CSS) plus Aurora-JS-TW and SplitText-TS-TW — all install cleanly. Stylesheets land next to their component and every relative import resolves; Hyperspeed still gets HyperSpeedPresets alongside it.
  • Asserted across all 664 generated items: 292 CSS entries, each registry:file with a matching @components/<Name>.css target; every other file still registry:component with no target; every ./*.css import in a shipped source file has a matching shipped stylesheet, and no stylesheet is shipped unused.
  • npm run build passes. npx prettier --check jsrepo.config.ts passes.
  • npm run lint reports 46 errors, all pre-existing in src/**/*.jsx — eslint runs with --ext js,jsx, so it doesn't cover either file this PR changes.

Out of scope

  • Lanyard's card.glb / lanyard.png still aren't shipped through the registry. They were already excluded before this change, and the component's docs tell users to supply them.
  • Lanyard's dependencyResolution: 'manual' still leaves its dependencies empty — separate issue.

The shadcn CLI runs every file it installs through its JavaScript/TypeScript
transformer unless the file is typed registry:file. Components were shipped as
whole folders and a folder cannot declare a type per file, so stylesheets went
out as registry:component and got parsed as JavaScript, failing every -CSS
variant with "Unexpected token (1:0)" on the first character of the CSS.

Declare stylesheets as registry:file, which shadcn copies verbatim. That type
requires an explicit target, so point it at @components/<Name>.css: shadcn
resolves the alias to the components directory configured in the user's
components.json, which is where the component itself lands, keeping the
component's relative ./<Name>.css import working.

Variants that ship a stylesheet are now listed file by file to give the
stylesheet its own type; every other variant still ships as a folder, so all
-TW entries are unchanged.

Closes DavidHDev#1049
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG]: Error: "Unexpected token (1:0)" when trying to install @react-bits/Lanyard-JS-CSS via shadcn CLI

1 participant