nuxt
4.6.4 · 2 Nov 2026MIT3.6M / weekRepositoryHomepagenpmAtom feed
Upgrading nuxt From 3.3.3 to 3.4.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 6
- changes to make
- 0
- advisories fixed
- 20
- new
- 9
- fixes
Before you upgrade
Tick each one off as you go- Breaking3.4.0
- Breaking3.4.0
- Breaking3.4.0
- Breaking3.4.0
- Breaking3.4.0
- Deprecated3.4.0
Security
15 advisories still affect 3.4.0
- Nuxt: Unauthorized Component Instantiation via Server Island Propsmoderate · GHSA-48hr-524c-v5w3
- Nuxt: Reflected XSS in `<NuxtLink>` via unsanitised `javascript:` or `data:` URLmoderate · GHSA-934w-87qh-qr26
- Nuxt: Server-Side Remote Code Execution via Runtime Template Injection in Nuxt Server Island Propshigh · GHSA-9473-5f9j-94wq
No published version clears them all yet.
Release by release
- Breaking
Previously it was possible to pass the
x-nuxt-no-ssrheader (undocumented) to force SPA rendering. We've now disabled this behaviour by default but you can get it back by settingexperimental.respectNoSSRHeaderto true. Alternatively, you can setevent.context.nuxt.noSSRon the server to force SPA rendering. - Breaking
We've removed the (deprecated)
#headalias and also disabled the polyfill for@vueuse/headbehaviour by default. (It can still be enabled withexperimental.polyfillVueUseHead.) - Breaking
We've removed the (deprecated)
experimental.viteNodeoption. It can be configured instead withvite.devBundler. - Breaking
We've deprecated accessing public runtime config without the
publickey. This was an undocument compatibility measure with Nuxt 2 and we plan to remove it entirely in v3.5.
- Breaking
23 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.