You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Those two project only have slight difference on components.json setting, which I think is very easy to modify to support different framework
So here is the idea:
Maybe we can separate the registry and cli repo, and rename cli to make it framework agnostic.
So that every framework can fit into this tool, share the same infrastructure but using different registry.
WDYT? leave your comment below, let's discuss about this.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
After some exploration on cli
I notice that we can leverage shadcn/ui's registry feature to reuse shadcn/ui's cli.
That means we can use shadcn/ui's cli to generate vue component using shadcn-vue's registry.
components.json
CLI
Those two project only have slight difference on
components.json
setting, which I think is very easy to modify to support different frameworkSo here is the idea:
Maybe we can separate the registry and cli repo, and rename cli to make it framework agnostic.
So that every framework can fit into this tool, share the same infrastructure but using different registry.
WDYT? leave your comment below, let's discuss about this.
Beta Was this translation helpful? Give feedback.
All reactions