Projects and Nuxt Doctor
Create an app, prepare its tooling, and inspect version findings.
Create an application#
Choose the Nuxt project entry in File → New → Project. Review the destination and options for the official nuxi init workflow. Install dependencies and run the generated dev script before modifying the starter.
The wizard creates normal configurations for the project’s common scripts. For an existing application, use its existing package-manager commands and environment values.
Inspect project health#
Open Nuxt Pro and review detected versions and scripts. Nuxt Doctor resolves installed Nuxt and DevTools versions from dependencies or npm, pnpm, Yarn, and Bun lockfiles. It separates lifecycle findings from security-version findings.
The documented release warns below Nuxt 4.5.1, Nuxt 3.21.10, and DevTools 3.3.1. These thresholds are release-specific; check the framework’s current guidance before selecting an upgrade. Doctor offers a copyable npx nuxt upgrade --dedupe command for review; copying it does not upgrade the project.
Work with framework diagnostics#
Stable Nuxt error codes such as NUXT_E1001 in run/debug consoles link to their framework documentation. Follow the code to understand the failure, then adjust source or configuration and rerun the relevant script.
Use Nuxt and Nitro live templates for pages, composables, plugins, and API handlers, then review the generated code in the context of your framework version.
Manual for version 2026.1.3 · Reviewed