Options to install modules on `nuxi init`
Opened this issue · 2 comments
Description
In the latest LearnVue's YouTube video(tagged with the timestamp), he has a great idea for setting up desired modules with Nuxt via the command line. This is a great idea that prevents people from scouring the internet/GitHub for templates or spending extra time copy-pasting commands after the initial setup.
I'm unsure about this since there are multiple ways to add modules, like nuxi module add <module> etc
Also, how will you determine which modules are "common" and should be included in the init command?
IMO, this will just be adding unnecessary friction for users who don’t care particularly about modules until they need them...
The outcome is only one regardless of the multiple ways to add modules. So I don't see that as an issue. Deducing "common" modules is not that difficult. There are tons of Nuxt projects and taking a look at some stats, we can figure that out. For instance, I am sure Eslint, testing, and Tailwind are some modules that most developers would like to have.