Repository navigation
Replace custom CLI with official shadcn CLI support
#2782
Nickersoft
started this conversation in
Ideas
Replies: 1 comment 2 replies
|
There are a lot of reasons that we can't use the shadcn cli but just to list a few:
But the main thing is the initialization |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Forgive me if there's something obvious I'm missing here, but with shadcn officially supporting third-party registries now and generalizing their JSON schema to allow the distribution of any kind of code, I'm wondering why this project still maintains its own CLI package as opposed to just exposing the Svelte components as official shadcn registry items.
From what I can tell, this project tries to keep itself pretty aligned with React shadcn from a configuration standpoint, so I would think the CLI doesn't really need any Svelte-specific features. Could make it easier for folks who may be using cross-framework projects (in something like Astro) or for devs like myself that would just like to use a single CLI to pull in all my code.
All reactions