nuxt@4.6.0
Wait — 4.6.4 is the safer choice for now.
18 issues mention 4.6.0 within 14 days of release (usual for this project: 1).
Why this verdict
- 18 issues mention 4.6.0 within 14 days of release (usual for this project: 1).Evidence
- 7 known advisories (worst: moderate), no fixed version found on this major.Evidence
- Release notes list 5 breaking changes: Node.js minimum version is now v22.21+, v24.11+ or v26+.Evidence
Confidence 100% · algorithm v1 · computed 2026-11-22. How verdicts work
Supply chain and security
- Malware reports
- None known (OSV)
- Known advisories
- 7 known
- License
- MIT
- Install scripts
- None
- Build provenance
- Signed provenance
- Weekly downloads
- 35,932
- GHSA-96x6-fvhx-49hgNuxt exposes the message and data of unhandled errors thrown during server rendering
- GHSA-9v7c-q64q-vv33Nuxt: Dot segments in the request path bypass `server/middleware` path checks and server route rules on page routes
- GHSA-f3x9-2chm-73c8Nuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on catch-all page routes
- GHSA-hf59-9xwc-2g4pNuxt: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)
- GHSA-r9jc-w898-3fv6Nuxt payload URL generation has quadratic cost for repeated slashes in the request path
- GHSA-vjh5-4x84-xrqpNuxt: Server-side route rules (`redirect`, `headers`, `proxy`, `ssr`) are skipped for case-variant paths when routing is case-insensitive
- GHSA-xfq5-w38q-pc2xNuxt server islands render `useHeadSafe` input without sanitisation
Compatibility
No compatibility boundary is crossed: this is a patch or minor release on a stable major.
Breaking changes in the release notes
- Node.js minimum version is now v22.21+, v24.11+ or v26+.“we require Node.js v22.21+, v24.11+ or v26+”
- The old "nuxt init" command is removed; only "npm create nuxt@latest" is supported.“we drop nuxt init and only support npm create nuxt@latest”
- Support for Nuxt 2 and @nuxt/bridge has been dropped.“Nuxt 2 and @nuxt/bridge are no longer supported”
- Mixing imports from h3 and nuxt/server now triggers a NUXT E8012 error.“If you mix the two, you'll see a NUXT E8012 error which should tell you which import to change”
- Several server helpers now behave differently: sendRedirect returns a response, createError takes status and statusText, and response headers are set via event.res.headers.“A few helpers also behave differently from their h3 v1 namesakes: sendRedirect returns the response rather than sending it, createError takes status and statusText, and response headers are set through event.res.headers”
AI-extracted from the official release notes and checked against the quoted text. Read the source
18 issues mention this version in nuxt/nuxt within 14 days of release. See them on GitHub
Check the official release notes below for behaviour changes before merging.
Release notes
Read the Nuxt changelog on Changes.Watch or the package page on npm for this version’s features and fixes.
New in this release
- Nuxt CLI v4 is shipped as a dependency and installed automatically.“Alongside the release of Nuxt v4.6, today also brings a new major release of the Nuxt CLI: @nuxt/cli v4 . It ships as a dependency of nuxt, so you'll get it automatically when you upgrade.”
- The dev command now shows an interactive terminal UI with panels for logs, routes, and network requests.“nuxt dev: an interactive terminal UI , showing URLs, startup progress and keyboard shortcuts, with panels to dive into error logs, routes, network requests and more”
- A lock file in .nuxt/ enables a second nuxt dev process to take over or defer to the first.“a lock file in .nuxt/, which lets a second nuxt dev (say, one started by an agent) take over or defer to the one you started”
- New "nuxt curl" and "nuxt task" commands can communicate with the running server.“powers new nuxt curl and nuxt task commands that talk to the running server”
- Introduced a new import source "nuxt/server" for server‑only code such as handlers and middleware.“nuxt/server is a new import source for server code: handlers, middleware and utilities a complement to nuxt/app.”
- Experimental @nuxt/vite server implementation allows pure Vite server builds.“we are also announcing a second, experimental implementation, @nuxt/vite server, which allows pure Vite server builds using the Vite Environment API.”
- A root application secret (runtimeConfig.appSecret) is now provided and used to derive module‑specific secrets.“Nuxt now has a root application secret: runtimeConfig.appSecret, set with NUXT APP SECRET”
- Session helpers are added to nuxt/server, storing sealed cookies with iron.“The first thing to use it is a set of session helpers in nuxt/server”
AI-extracted from the official release notes and checked against the quoted text. Read the source
Popular issues closed in this release window
- #29624 Cannot read properties of undefined (reading ‘default’) · 35 reactions
- #15261 Types in body/params when fetching server side routes · 30 reactions
- #14584 optimisations for prefetching chunks · 26 reactions
- #18718 support prerendering error pages · 24 reactions
Deprecations and deadlines
The maintainer has not deprecated this version on npm.
Did upgrading to 4.6.0 work for you?
Results appear once three developers have voted.