nuxt
4.6.4 · 2 Nov 2026MIT3.6M / weekRepositoryHomepagenpmAtom feed
Upgrading nuxt From 4.6.3 to 4.6.4
1 release in betweenevery note read
Reading releases, release notes and advisories…
Before you upgrade
Tick each one off as you go- Breaking4.6.4
Security
4 advisories still affect 4.6.4
- Nuxt exposes the message and data of unhandled errors thrown during server renderingmoderate · GHSA-96x6-fvhx-49hg
- 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
- Nuxt: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)low · GHSA-hf59-9xwc-2g4p
- Nuxt: Server-side route rules (`redirect`, `headers`, `proxy`, `ssr`) are skipped for case-variant paths when routing is case-insensitivemoderate · GHSA-vjh5-4x84-xrqp
No published version clears them all yet.
Fixes 1 advisory affecting 4.6.3
- Nuxt payload URL generation has quadratic cost for repeated slashes in the request pathmoderate · GHSA-r9jc-w898-3fv6
Release by release
- Breaking
nitro,nuxt: require unrouting 0.3.2
- Fixed
nuxt: use unambiguous encoding for island hash
- Fixed
nuxt: do not expose details of untrusted thrown errors
- Fixed
nuxt: strip trailing slashes in linear time
- Breaking
5 other lines we could not sort, mostly version bumps
- 4.6.4
Error details in production. When a page fails to render on the server, the error page and the payload now only carry message and data of errors you create with
createError. Everything else is stripped. - 4.6.4
Dev server
Hostchecks. Webpack and rspack dev servers now reject requests with an unexpectedHostheader, as Vite already does. If you use a custom hostname or tunnel, you'll need to add it to the newdevServer.allowedHostsoption. - 4.6.4
workspaceDirdetection. WhenworkspaceDirisn't set, Nuxt now only widens it pastrootDirto an explicit workspace root or the closest git repository. - 4.6.4
Nitropack cached routes.
cache,swrandisrroute rules now only cacheGETandHEADrequests, and no longer store responses that set a cookie or sendCache-Control: privateorno-store. Wildcardproxyandredirectrules also reject requests whose resolved target would leave the rule's scope. - 4.6.4
Route rules and encoded slashes. Route rules now match paths that contain encoded slashes, so
/api%2Fadminis covered by a/api/**rule.
16 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.