nuxt
4.6.4 · 2 Nov 2026MIT3.6M / weekRepositoryHomepagenpmAtom feed
Upgrading nuxt From 2.18.0 to 4.6.0
116 releases in betweennotes for 110
Reading releases, release notes and advisories…
Counted from 110 of 116 release notes. Advisories are counted from the advisory database, in full.
Start here
Before you upgrade
Tick each one off as you go- Breaking4.5.0
- Breaking4.5.0
- Breaking4.2.0
- Breaking4.2.0
- Breaking4.2.0
- Breaking4.2.0
- Breaking4.2.0
- Breaking4.1.1
- Breaking4.0.0
- Breaking4.0.0
Security
7 advisories still affect 4.6.0
- Nuxt exposes the message and data of unhandled errors thrown during server renderingmoderate · GHSA-96x6-fvhx-49hg
- Nuxt: Dot segments in the request path bypass `server/middleware` path checks and server route rules on page routesmoderate · GHSA-9v7c-q64q-vv33
- Nuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on catch-all page routesmoderate · GHSA-f3x9-2chm-73c8
No published version clears them all yet.
Fixes 3 advisories affecting 2.18.0
- Nuxt: Incomplete fix for GHSA-934w-87qh-qr26: a `javascript:` URL prefixed with an ASCII control character executes from `<NuxtLink>` when `pages` is disabledlow · GHSA-jjm6-p2m9-9w4x
- Cross-site scripting via <NoScript> slot content in Nuxt's head componentslow · GHSA-m3q2-p4fw-w38m
- nuxt vulnerable to Cross-site Scripting in navigateTo if used after SSRmoderate · GHSA-vf6r-87q4-2vjf
- 4.6.0
- 4.6.0
- 4.6.0
- 4.5.1
If you already upgraded for the earlier route rule advisory (CVE-2026-53721), you still need this release: one of the fixes addresses a regression introduced by that fix.
- 4.5.1
Full details: Nuxt Security Patch Releases and GitHub Security Advisories.
- 4.4.7
nuxt: Block path-normalization open redirect in
navigateTo - 3.8.0
Remove huntr + encourage GitHub vulnerability reporting
Release by release
- Security
- Security
- Security
- Deprecated
schema: deprecate
nitro.*options duplicated at the top level
- New
nuxt,kit: Skip rewriting unchanged generated files
- New
kit,nuxt: Use lazy imports to improve parsing speed
- New
vite: Skip html entry probes in bare-import resolver
- New
nuxt: Reuse app and component scans for unchanged structures
- New
- Security
If you already upgraded for the earlier route rule advisory (CVE-2026-53721), you still need this release: one of the fixes addresses a regression introduced by that fix.
- Security
Full details: Nuxt Security Patch Releases and GitHub Security Advisories.
- New
nitro: Replace island teleports in a single html pass
- New
nuxt: Add
vue.optionsApiand disable it for v5+
- Security
- Breaking
If you want to test some of the breaking changes of Nuxt v5, you can already opt in with future.compatibilityVersion: 5.
- Breaking
The runtime behaviour is compatible for the vast majority of apps, and promise input (deprecated in v2) is no longer supported.
- New
The dev server now runs in middleware mode via Rsbuild, replacing
webpack-dev-middlewareandwebpack-hot-middleware(#35575). - New
We use an Rspack-specific Vue loader for correct SSR scoped-style ids and stricter ESM resolution (#35566).
- Breaking
- Fixed
vite: Shorter socket name for macOs with tmp fallback
- Fixed
kit: Respect
typeoption infindPath - Fixed
deps: Update nuxt/scripts presets
- Fixed
nuxt: Revert unhead dependency back to v2
- Fixed
- Security
nuxt: Block path-normalization open redirect in
navigateTo - Fixed
nitro: Assign
noSSRbefore deciding payload extraction - Fixed
vite: Avoid filtering out dirs with shared prefix from
allowDirs - Fixed
nuxt: Use resolve from
pathefor buildCache path boundary check
- Security
- New
nitro: Add json extension to payload cache items
- Fixed
vite: Use spa entry for vite-node fallback
- Fixed
vite: Invalidate SSR module cache when modules are invalidated via plugin hooks
- Fixed
nuxt: Match deduplicated
resolveComponentcalls in jsx blocks
- New
- New
kit: Cache layer roots and short-circuit
isIgnoredrelative - Fixed
vite: Resolve vite
clientServerwithssr: false - Fixed
nitro: Correct payload route rule for
/+ overridessr: true - Fixed
nitro: Break recursive rendering deadlocks during prerender
- New
20 other lines we could not sort, mostly version bumps
- 4.6.0
an interactive terminal UI, showing URLs, startup progress and keyboard shortcuts, with panels to dive into error logs, routes, network requests and more
- 4.6.0
the dev server gives you more info, such as why it reloaded or restarted, which
nuxt.configkeys changed, where the time went during a slow start or build, and how long each module took to set up - 4.6.0
it smooths the upgrade to Nuxt 5, which moves to Nitro v3 and h3 v2. Server code written against
nuxt/serveron 4.6 runs unchanged there, so a module can ship one file for both. - 4.6.0
it decouples Nuxt from the Nitro release cycle. Because we 'own' the API, we can adapt to breaking changes in Nitro or h3 without requiring a future major - and we can release Nuxt majors without having to wait for upstream releases.
- 4.6.0
it makes Nuxt's code more maintainable. It helps us preserve the separation of concerns between our API -
/appand/server- and the bundler + server that you ultimately want to build your app. - 4.3.0
All the same features: Route rule layouts, ISR payload extraction, layout props with
setPageLayout,#serveralias, draggable error overlay, and more - 4.3.0
All performance improvements: SSR styles optimization, hook filters, and route rules compilation
- 4.3.0
Module disabling: Disable layer modules by setting options to
false - 4.3.0
Critical bug fixes: Async data reactivity in Options API,
useCookienumber parsing, head component deduplication, and more - 4.0.0
Nuxt 2 compatibility has been removed from
@nuxt/kit. (This will particularly affect module authors.)
2497 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.