nuxt
4.6.4 · 2 Nov 2026MIT3.6M / weekRepositoryHomepagenpmAtom feed
3.21.11 is the newest release of 3.x.
In short
31 new27 fixed37 internal
Security
16 advisories affect 3.5.0; 4.6.0 fixes the others
- ModerateNuxt exposes the message and data of unhandled errors thrown during server renderingGHSA-96x6-fvhx-49hg · 16 Nov 2026No fix yet
- ModerateNuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on catch-all page routesGHSA-f3x9-2chm-73c8 · 16 Nov 2026No fix yet
- ModerateNuxt: Server-side route rules (`redirect`, `headers`, `proxy`, `ssr`) are skipped for case-variant paths when routing is case-insensitiveGHSA-vjh5-4x84-xrqp · 22 Oct 2026No fix yet
- CriticalNuxt vulnerable to remote code execution via the browser when running the test locallyGHSA-v784-fjjh-f8r4 · 5 Aug 2024Fixed in 3.12.4
- HighNuxt: Unauthenticated CPU exhaustion parsing and hashing the Nuxt island endpoint body before hash validationGHSA-9pgf-384g-p7mv · 5 Aug 2026Fixed in 3.21.10
11 more
- HighNuxt: Server-Side Remote Code Execution via Runtime Template Injection in Nuxt Server Island PropsGHSA-9473-5f9j-94wq · 5 Aug 2026Fixed in 3.21.10
- HighNuxt: Unauthenticated out-of-memory crash via unbounded v-for expansion in island renderingGHSA-hxcr-hm88-mpq6 · 5 Aug 2026Fixed in 3.21.10
- HighNuxt allows DOS via cache poisoning with payload rendering responseGHSA-jvhm-gjrh-3h93 · 19 Mar 2025Fixed in 3.16.0
- ModerateNuxt: Unauthorized Component Instantiation via Server Island PropsGHSA-48hr-524c-v5w3 · 5 Aug 2026Fixed in 3.21.10
- ModerateNuxt: Reflected XSS in `<NuxtLink>` via unsanitised `javascript:` or `data:` URLGHSA-934w-87qh-qr26 · 16 Jun 2026Fixed in 3.21.7
- ModerateNuxt: URL-handling weaknesses in `navigateTo` and `reloadNuxtApp`: SSR open redirect, client-side script execution via the `open` option, and protocol-relative bypass in `reloadNuxtApp`GHSA-c9cv-mq2m-ppp3 · 16 Jun 2026Fixed in 3.21.7
- ModerateNuxt: Reflected XSS in `navigateTo()` external redirectGHSA-fx6j-w5w5-h468 · 19 May 2026Fixed in 3.21.6
- Moderatenuxt vulnerable to Cross-site Scripting in navigateTo if used after SSRGHSA-vf6r-87q4-2vjf · 5 Aug 2024Fixed in 3.12.4
- LowNuxt: Incomplete fix for GHSA-934w-87qh-qr26: a `javascript:` URL prefixed with an ASCII control character executes from `<NuxtLink>` when `pages` is disabledGHSA-jjm6-p2m9-9w4x · 22 Oct 2026Fixed in 4.6.0
- LowCross-site scripting via <NoScript> slot content in Nuxt's head componentsGHSA-m3q2-p4fw-w38m · 16 Jun 2026Fixed in 3.21.7
- LowNuxt: `__nuxt_island` endpoint does not bind responses to request props, enabling shared-cache poisoningGHSA-g8wj-3cr3-6w7v · 19 May 2026Fixed in 3.21.6
Release note
3.5.0 is a minor (feature) release with lots of new features to play with.
Highlights
Vue 3.3 released!
Vue 3.3 has been released, with lots of exciting features, particularly around type support. This also brings a significant improvement to data fetching when navigating between nested pages (#20777), thanks to @antfu and @baiwusanyu-c.
New
defineOptionsmacro'generic' components
Typed slots and using external types in defineProps
... and more
Read the full release announcement for more details.
Nitropack v2.4
We've been working on lots of improvements to Nitro and these have landed already in Nitro v2.4 - you may already have this upgrade, which contains a lot of bug fixes, updates to the module worker format for Cloudflare, Vercel KV support and more.
One note: if you're deploying to Vercel or Netlify and want to benefit from incremental static regeneration, you should now update your route rules:
routeRules: {
-- '/blog/**': { swr: 3000 },
++ '/blog/**': { isr: 3000 },
}Read the full release notes.
New defaults
Rich JSON payload serialisation is now enabled by default (#19205, #20770). This is both faster and allows serialising complex objects in the payload passed from the Nuxt server to client (and also when extracting payload data for prerendered sites).
This now means that various rich JS types are supported out-of-the-box: regular expressions, dates, Map and Set and BigInt as well as NuxtError - and Vue-specific objects like ref, reactive, shallowRef and shallowReactive.
You can find an example in our test suite.
This is all possible due to Rich-Harris/devalue#58. For a long time, Nuxt has been using our own fork of devalue owing to issues serialising Errors and other non-POJO objects, but we now have transitioned back to the original.
You can even register your own custom types with a new object-syntax Nuxt plugin:
export default definePayloadPlugin(() => {
definePayloadReducer('BlinkingText', data => data === '<original-blink>' && '_')
definePayloadReviver('BlinkingText', () => '<revivified-blink>')
})You can read more about how this works here.
Interactive server components
This feature should be considered highly experimental, but thanks to some great work from @huang-julien we now support interactive content within server components via slots (#20284).
You can follow the server component roadmap at #19772.
Environment config
You can now configure fully typed, per-environment overrides in your nuxt.config:
export default defineNuxtConfig({
$production: {
routeRules: {
'/**': { isr: true }
}
},
$development: {
//
}
})If you're authoring layers, you can also use the $meta key to provide metadata that you or the consumers of your layer might use.
Read more: #20329.
Fully typed pages
You can benefit from fully typed routing within your Nuxt app via this experimental integration with github.com/posva/unplugin-vue-router - thanks to some great work from @posva! Out of the box, this will enable typed usage of navigateTo, <NuxtLink>, router.push() and more. You can even get typed params within a page by using const route = useRoute('route-name').
export default defineNuxtConfig({
experimental: {
typedPages: true
}
})'Bundler' module resolution
We now have full support within Nuxt for the bundler strategy of module resolution. We would recommend adopting this if possible. It has type support for subpath exports, for example, but more exactly matches the behaviour of build tools like Vite and Nuxt than Node16 resolution.
export default defineNuxtConfig({
typescript: {
tsConfig: {
compilerOptions: {
moduleResolution: 'bundler'
}
}
}
})This turns on TypeScript's ability to 'follow' Node subpath exports. For example, if a library has a subpath export like mylib/path that is mapped to mylib/dist/path.mjs then the types for this can be pulled in from mylib/dist/path.d.ts rather than requiring the library author to create mylib/path.d.ts.
Separate server types
We plan to improve clarity within your IDE between the 'nitro' and 'vue' part of your app, and we've shipped the first part of this via a separate generated tsconfig.json for your ~/server directory (#20559). You can use by adding an additional ~/server/tsconfig.json with the following content:
{
"extends": "../.nuxt/tsconfig.server.json"
}Although right now these values won't be respected when type checking, you should get better type hints in your IDE.
Deprecations
Although we have not typed or documented the build.extend hook from Nuxt 2, we have been calling it within the webpack builder. We are now explicitly deprecating this and will remove it in a future minor version.
Upgrading
As usual, our recommendation for upgrading is to run:
nuxi upgrade --force
This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
Changelog
Enhancements
kit: Add
prependoption toaddImportsDirnuxt: Add scoped helper for clearing error within boundary
nuxt: Auto import 'watchPostEffect' and 'watchSyncEffect' from vue
vite: Introduce
vite:configResolvedhookwebpack: Introduce
webpack:configResolvedhookkit: Allow vite and webpack plugins to be prepended
nuxt: Add layer meta and env overrides to config types
test-utils: Add option to configure test server port
nuxt: Allow access to components within app
kit: Support passing getter to
addVitePluginandaddWebpackPlugincli: Allow greater control of
nuxi analyzefrom clinuxt: Add
nuxtApp.runWithContextdeps: Upgrade to nitropack v2.4
nuxt: Add experimental
typedPagesoptionnuxt: Add apps to nuxt build-time instance
cli: Allow passing overrides to other nuxi commands
schema: Enable rich json payloads by default
nuxt: Use
runWithContextwithincallWithNuxtnuxt: Add
useRequestURLhelpernuxt: Allow fallback production content in
<DevOnly>kit:
addBuildPluginfor builder-agnostic implementationnuxt: Allow keeping fallback for
NuxtClientFallbacknuxt: Support separate server tsconfig
nuxt: Full scoped slots support for server components
nuxt: Support parallel plugins
Fixes
nuxt: Remove backwards-compatible runtimeConfig proxy
nuxt: Add
@nuxt/devtoolsmodule before core modulesnuxt: Properly handle query for component wrapper
nuxt: Skip payload extraction for island context
nuxt: Remove internal
<FragmentWrapper>nuxt: Ensure
useErroris called with nuxt app contextnuxt: Run page meta plugin on all pages (and only pages)
nuxt, vite: Ignore
nuxt_componentssr style andisVuewebpack: Warn when using deprecated
build.extendhooknuxt: Allow resolving client nuxt app to singleton
nuxt: Generate empty sourcemaps for wrappers
nuxt: Prevent treeshaking hooks with composable names
kit: Prefer esm resolution for modules to install
vite: Expand
fs.allowdirs to include app filesnuxt: Deduplicate global components before registration
nuxt: Remove webstorm compatibility augmentation
nuxt: Enable suspensible behaviour for nested pages
cli: Hard-reload nuxt when
.envchangesnuxt: Avoid destructuring error prop (works around upstream bug)
nuxt: Always inline styles for server/island components
nuxt: Allow serialising undefined refs
nuxt: Transform client fallbacks directly on SFCs
vite: Dedupe/optimize more vue core deps
nuxt: Get fallback for
<DevOnly>from parsed htmlnuxt: Ensure all dir parts are present in component name
nuxt: Allow
pages:extendto enable pages modulenuxt: Stop loading indicator on vue errors
nuxt: Add types for webpack/vite environments
nuxt: Pass from + savedPosition to first
scrollBehavior
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.