feat(cli): add GitHub source registries, add-file, and eject#38
Merged
Conversation
Support the June 2026 GitHub source registry model and the May 2026 shadcn eject command. - Add a "github" distribution target: a public repo is the registry, with no framework app, build step, published JSON, or server. Scaffolds a minimal repo and emits `npx shadcn add <owner>/<repo>/<item>` install commands. Flags: --target, --github [owner/repo], --github-slug. - Add `add-file` to distribute arbitrary registry:file items (conventions, CI workflows, agent instructions, ~/-targeted files). - Add `eject` as a package-manager-aware passthrough to `shadcn eject`. - Install commands now auto-detect a github.com homepage across add-component, llms.txt, and .scn-stack.json. Bumps the package to 0.12.0.
- args parsing for --target / --github / --github-slug - githubSlugFromHomepage + GitHub-aware installCommand - integration tests for the minimal GitHub scaffold and add-file
Add cli/github-registries.mdx and cli/eject.mdx, a Distribution prompt section, updated options/flags tables, landing-page callout, and README features.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
docs
This was referenced Jun 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds first-class support for the two latest shadcn updates:
githubdistribution target. A public repo is the registry: no framework app, noshadcn build, no published JSON, no server. Scaffolds a minimal repo and emitsnpx shadcn add <owner>/<repo>/<item>install commands everywhere. New flags:--target,--github [owner/repo],--github-slug, plus a Distribution prompt.add-file— distribute arbitraryregistry:fileitems (project conventions, CI workflows, agent instructions,~/-targeted files), supporting--file path:target(repeatable) and--target.eject(May 2026) — a package-manager-aware passthrough toshadcn eject(inlineshadcn/tailwind.css, drop theshadcndep), with-c <workspace>for monorepos.Install-command resolution now auto-detects a github.com homepage across
add-component,llms.txt, and.scn-stack.json. Bumps the package to 0.12.0 (also releasing the previously-unreleased 0.11.0 work).Why
The June 2026 GitHub source-registry model is the new default path for "I just want to share components from a repo," and scn-stack was over-scaffolding (framework app + build + host) for that case. This makes the build-less path a first-class target and lets registries distribute non-component items.
Closes #
Type
feat— New featureChecklist
feat/,fix/,docs/, etc.)npm run lintpassesnpm testpassesScreenshots