10 / 11
create-nuxt-primevue
Open source · 2026
An npm CLI that starts Nuxt 4 projects on the last MIT versions of PrimeVue, and checks existing projects before a licence change catches them out.
- 100%Mutation score on the critical modules
- 369Automated tests
- 4Package managers tested in CI

Overview
The problem
npm install primevue now installs version 5, which left the MIT licence. Without a licence key, a red badge sits on every page, and nothing fails: the install works and the build passes. primeicons and @primeuix/themes moved too, on different version numbers, so fixing one package isn’t enough.
Setting up this stack already cost me time on every client project: the right versions, Tailwind’s CSS layers against PrimeVue’s styles, the theme, the fonts.
The fix
Two commands. npm create nuxt-primevue@latest creates a Nuxt 4 project on the last MIT versions, with your theme, primary colour and font, and the whole stack already wired up. npx create-nuxt-primevue doctor scans an existing project, shows the exact changes, and applies them only with your consent and a clean git tree.
Generated projects also run a licence guard as part of the build. Only the exact licence MIT passes, and it fails closed: if a declared package isn’t installed, the build stops.
The result
Version 1.0.0 is on npm. The tests cover critical behaviour only and are proven by mutation testing, with a floor of 100% on the critical modules. CI builds real projects with npm, pnpm, Yarn and bun on Linux, and npm on Windows. A browser check must also find the licence badge on a deliberate version 5 install, so a passing result means something. A public guide covers the licence change and thirteen problems in this stack.
Architecture
- CLITypeScript; four questions or flags, then the install with the project’s package manager and a first commit
- TemplateNuxt 4, PrimeVue 4.5.5 and Tailwind 4 with the CSS layers in order, exact version pins, self-hosted fonts
- Licence guardA script with no dependencies, inside the build: only the exact licence MIT passes, and it fails closed
- doctorReuses the guard to scan existing projects, and changes pins only with consent and a clean git tree
Key decision
Run the licence guard inside the build script, not in a prebuild hook. Yarn 2 and later skip pre hooks, and a check that silently never runs is worse than no check.
