nuxt
4.6.4 · 2 Nov 2026MIT3.6M / weekRepositoryHomepagenpmAtom feed
Upgrading nuxt From 4.5.2 to 4.6.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
Start here
Before you upgrade
Tick each one off as you go- Deprecated4.6.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 1 advisory affecting 4.5.2
- 4.6.0
- 4.6.0
- 4.6.0
Release by release
- Security
- Security
- Security
- Deprecated
schema: deprecate
nitro.*options duplicated at the top level
5 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.
117 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.