Nuxt Installation Template Selection Feels Blind
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 399
- Forks
- 119
- Avg merge
- 20h 59m
- Merged PRs (30d)
- 65
Description
It looks like the Nuxt installation flow has changed, and I’m not a fan of making blind selections.
Which template would you like to use?
│ ○ content – Content-driven website
│ ● minimal – Minimal setup for Nuxt 4 (recommended)
│ ○ module – Nuxt module
│ ○ ui – App using Nuxt UI
The options don’t make it clear what will or won’t be included in each template. I prefer starting with a blank project, but even when selecting “module – Nuxt module”, it installs several things I don’t need. The previous manual setup was much clearer.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Nuxt installation flow and inspect the template-selection prompt shown in the issue. Compare what each listed template installs, especially the module option, and use that comparison to define clearer template descriptions or selection behavior. Done means users can understand the included setup before choosing a template.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt, typescript
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100