Re:Shadxn: An experimental CLI tool that builds upon shadcn-...
by verdverm on Monday February 12, 2024 @12:45PM
(#39347884)
It sits in a weird place because
1. Some things are added to your project through package.json the normal way
2. Some things are added to your project by vendoring (copy/paste) a file or two, now with configurable source
I can imagine companies wanting a consistent set of components that are easily installed (hence shadxn), but why not turn that into an internal/private npm module?
1. Some things are added to your project through package.json the normal way
2. Some things are added to your project by vendoring (copy/paste) a file or two, now with configurable source
I can imagine companies wanting a consistent set of components that are easily installed (hence shadxn), but why not turn that into an internal/private npm module?