Repository navigation
Replies: 1 comment
|
I understand the convenience of having Tailwind-enabled templates, but adding UI frameworks or component libraries to create-vite, a general-purpose scaffolding tool ,may lead to significantly increased maintenance overhead. There are many UI frameworks and preferences vary widely among developers, so choosing which ones to include could be contentious. If you frequently use a specific combination, it's probably better to create and maintain a custom template in your own library, and use that for new projects. This approach keeps create-vite lightweight and flexible for everyone. |
0 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.
Discussion: Add Tailwind-enabled templates to
create-viteContext
create-vitealready provides excellent starter templates for frameworks like React, Vue, and Svelte.However, most developers using these frameworks end up integrating Tailwind CSS immediately after project setup.
This repeated setup step—though simple—feels like something that could easily be automated within the initial template choices.
💭 Idea
Instead of introducing new CLI flags or plugin systems, simply expand the default template catalog to include Tailwind-enabled versions.
Example Usage
All reactions