Skip to content

Install from the GitHub repository - #16

Merged
WaylandYang merged 1 commit into
devfrom
feat/github-registry
Oct 14, 2026
Merged

WaylandYang merged 1 commit into
devfrom
feat/github-registry

Conversation

@WaylandYang

Copy link
Copy Markdown
Collaborator

What

As suggested in shadcn-ui/ui#12283, install from the repository with GitHub Registries.

  • Docs, README, Create's Get Code and the Blocks page give npx shadcn@latest add deeplethe/solid-glass/<item>.
  • registry.json: Solid Glass's own components name one another as deeplethe/solid-glass/<item>, so an item installed from a tag or commit brings the others from the same one.
  • public/r/ (served by the site) still names them by the site's address, so …/r/<item>.json keeps working with an older CLI.

Checked

  • npx shadcn@latest registry validate deeplethe/solid-glass#<this commit>: 14 items valid
  • In a fresh Vite + shadcn project: add deeplethe/solid-glass/solid-glass#<sha> and …/agent-workspace#<sha> install the stylesheet, the block and its nine own components; tsc -b and vite build pass
  • npm run docs, npm run typecheck, npm run build

🤖 Generated with Claude Code

The docs, the README, Create and the Blocks page now give the short
address, deeplethe/solid-glass/<item>, which the shadcn command line
reads straight from the repository. In registry.json Solid Glass's own
components name one another the same way, so an item installed from a
tag or a commit brings the rest from the same one. What the site
serves under /r/ still names them by the site's address, for an older
command line.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: WaylandYang <145302500+WaylandYang@users.noreply.github.com>
@WaylandYang
WaylandYang merged commit 1318bb0 into dev Oct 14, 2026
4 checks passed
@WaylandYang
WaylandYang deleted the feat/github-registry branch October 14, 2026 13:58
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.

1 participant