@nuxt/rspack-builder
4.6.4 · 2 Nov 2026MIT590 / weekRepositoryHomepagenpmAtom feed
3.21.11 is the newest release of 3.x.
In short
1 removed24 new10 faster43 fixed14 changed87 internal
- Removed
Remove babel debugging plugin from jiti stub options
Security
2 advisories affect 3.21.0; 3.21.7 fixes them
- Moderate@nuxt/webpack-builder and @nuxt/rspack-builder dev server same-origin check bypassed when Sec-Fetch-Site, Origin, and Referer are all absent (incomplete fix for GHSA-6m52-m754-pw2g)GHSA-x6qj-4h56-5rj5 · 16 Jun 2026Fixed in 3.21.7
- ModerateNuxt: Dev server exposes built source over LAN to malicious sites (incomplete fix for GHSA-4gf7-ff8x-hq99)GHSA-6m52-m754-pw2g · 19 May 2026Fixed in 3.21.6
Release note
3.21.0 is the next minor release.
Nuxt 4.3 and 3.21 bring powerful new features for layouts, caching, and developer experience – plus significant performance improvements under the hood.
Some News
Extended v3 Support
Early this month, I opened a discussion to find out how the upgrade had gone from v3 to v4. I was really pleased to hear how well it had gone for most people.
Having said that, we're committed to making sure no one gets left behind. And so we will continue to provide security updates and critical bug fix releases beyond the previously announced end-of-life date of January 31, 2026, meaning Nuxt v3 will meet its end-of-life on July 31, 2026.
Tip
As usual, today also brings a minor release for v3, with many of the same improvements backported from v4.3.
Preparing for Nuxt 5
We're closer than ever to the releases of Nuxt v5 and Nitro v3. In the coming weeks, the main branch of the Nuxt repository will begin receiving initial commits for Nuxt 5. However, it's still business as usual.
Continue making pull requests to the
mainbranchWe'll backport changes to the
4.xand3.xbranches
Keep an eye out on the Upgrade Guide – we'll be adding details about how you can already start migrating your projects to prepare for Nuxt v4 with future.compatibilityVersion: 5.
Route Rule Layouts
But that's enough about the future. We have a lot of good things for you today!
First, you can now set layouts directly in route rules using the new appLayout property (#31092). This provides a centralized, declarative way to manage layouts across your application without scattering definePageMeta calls throughout your pages.
export default defineNuxtConfig({
routeRules: {
'/admin/**': { appLayout: 'admin' },
'/dashboard/**': { appLayout: 'dashboard' },
'/auth/**': { appLayout: 'minimal' }
}
})This might be useful for:
Admin panels with a shared layout across many routes
Marketing pages that need a different layout from the app
Tip
Plus, you can pass props to layouts now! See the setPageLayout improvements below.
ISR/SWR Payload Extraction
Payload extraction now works with ISR (incremental static regeneration), SWR (stale-while-revalidate) and cache routeRules (#33467). Previously, only pre-rendered pages could generate _payload.json files.
This means:
Client-side navigation to ISR/SWR pages can use cached payloads
CDNs (Vercel, Netlify, Cloudflare) can cache payload files alongside HTML
Fewer API calls during navigation – data can be prefetched and served from the cached payload
export default defineNuxtConfig({
routeRules: {
'/products/**': {
isr: 3600, // Revalidate every hour
}
}
})Dev Mode Payload Extraction
Related to the above, payload extraction now also works in development mode (#30784). This makes it easier to test and debug payload behavior without needing to run a production build.
Important
Payload extraction works in dev mode with nitro.static set to true, or for individual pages which have isr, swr, prerender or cache route rules.
Disable Modules from Layers
When extending Nuxt layers, you can now disable specific modules that you don't need (#33883). Just pass false to the module's options:
export default defineNuxtConfig({
extends: ['../shared-layer'],
// disable @nuxt/image from layer
image: false,
})Route Groups in Page Meta
Route groups (folders wrapped in parentheses like (protected)/) are now exposed in page meta (#33460). This makes it easy to check which groups a route belongs to in middleware or anywhere you have access to the route.
<script setup lang="ts">
// This page's meta will include: { groups: ['protected'] }
useRoute().meta.groups
</script>export default defineNuxtRouteMiddleware((to) => {
if (to.meta.groups?.includes('protected') && !isAuthenticated()) {
return navigateTo('/login')
}
})This provides a clean, convention-based approach to route-level authorization without needing to add definePageMeta to every protected page.
Layout Props with setPageLayout
The setPageLayout composable now accepts a second parameter to pass props to your layout (#33805):
export default defineNuxtRouteMiddleware((to) => {
setPageLayout('admin', {
sidebar: true,
theme: 'dark'
})
})<script setup lang="ts">
defineProps<{
sidebar?: boolean
theme?: 'light' | 'dark'
}>()
</script>#server Alias
A new #server alias provides clean imports within your server directory (#33870), similar to how #shared works:
// Before: relative path hell
import { helper } from '../../../../utils/helper'
// After: clean and predictable
import { helper } from '#server/utils/helper'The alias includes import protection – you can't accidentally import #server code from client or shared contexts.
Draggable Error Overlay
The development error overlay introduced in Nuxt 4.2 is now draggable and can be minimized (#33695). You can:
Drag it to any corner of the screen (it snaps to edges)
Minimize it to a small pill button when you want to keep working
Your position and minimized state persist across page reloads
This is a quality-of-life improvement when you're iterating on fixes and don't want the overlay blocking your view.
github.com/user-attachments/assets/nuxt_4-3_err…
Async Plugin Constructors
Module authors can now use async functions when adding build plugins (#33619):
export default defineNuxtModule({
async setup() {
// Lazy load only when actually needed
addVitePlugin(() => import('my-cool-plugin').then(r => r.default()))
// No need to load webpack plugin if using Vite
addWebpackPlugin(() => import('my-cool-plugin/webpack').then(r => r.default()))
}
})This enables true lazy loading of build plugins, avoiding unnecessary code loading when plugins aren't needed.
Performance Improvements
This release includes several performance optimizations for faster builds:
Hook filters - Internal plugins now use filters to avoid running hooks unnecessarily
SSR styles optimization - The
nuxt:ssr-stylesplugin is now significantly faster (#33862, #33865)Layer alias transform - Skipped when using Vite (it handles this natively)
Route rules compilation - Route rules are now compiled into a client chunk using
rou3, removing the need forradix3in the client bundle and eliminating app manifest fetches
Inline Styles for Webpack/Rspack
The inlineStyles feature now works with webpack and rspack builders (#33966), not just Vite. This enables critical CSS inlining for better Core Web Vitals regardless of your bundler choice.
Deprecations
statusCode → status, statusMessage → statusText
In preparation for Nitro v3 and H3 v2, we're moving to use Web API naming conventions (#33912). The old properties still work but are deprecated in advance of v5:
- throw createError({ statusCode: 404, statusMessage: 'Not Found' })
+ throw createError({ status: 404, statusText: 'Not Found' })Bug Fixes
Notable fixes in this release:
Fixed head component deduplication using
keyattribute (#33958, #33963)Fixed async data properties not being reactive in Options API
Fixed
useCookieunsafe number parsing during decodeFixed
NuxtPagenot re-rendering when nestedNuxtLayouthas layouts disabledFixed client-side pathname decoding for non-ASCII route aliases
Fixed suspense remounting when navigating after pending state
Fixed clipboard copy in error overlay
Enabled
allowArbitraryExtensionsby default in TypeScript configAdded
noUncheckedIndexedAccessto server tsconfig for safer typing
Important
Enabling noUncheckedIndexedAccess in the Nitro server TypeScript config improves type safety but may surface new type errors in your server code. This change was necessary because Nuxt's app context performs type checks on server routes (learn more).
While we recommend keeping this enabled for better type safety, you can disable it if needed:
export default defineNuxtConfig({
nitro: {
typescript: {
tsConfig: {
compilerOptions: {
noUncheckedIndexedAccess: false
}
}
}
}
}) Note that disabling this may allow type errors to slip through that could cause runtime issues with indexed access.
Nuxt 3.21.0
Alongside v4.3.0, we're releasing Nuxt v3.21.0 with many of the same improvements backported to the 3.x branch. This release includes:
All the same features: Route rule layouts, ISR payload extraction, layout props with
setPageLayout,#serveralias, draggable error overlay, and moreAll performance improvements: SSR styles optimization, hook filters, and route rules compilation
Module disabling: Disable layer modules by setting options to
falseCritical bug fixes: Async data reactivity in Options API,
useCookienumber parsing, head component deduplication, and more
Upgrading
Our recommendation for upgrading is to run:
npx nuxt@latest upgrade --dedupe --channel=v3
This will deduplicate your lockfile and help ensure you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.
Tip
Check out our upgrade guide if upgrading from an older version.
Changelog
Enhancements
kit: Support async constructor for adding plugins
kit: Export Nuxt major version type
schema: Add
#serveralias for server directory importsschema: Hoist nitro
crosswstypesnitro,nuxt: Compile route rules into client chunk
nuxt: Allow disabling modules by setting module options to
falsekit: Allow specifying
moduleDependenciesas an async functionnuxt: Support
appLayoutin route rulesnuxt: Add route groups to page meta
nuxt: Enable payload extraction for ISR/SWR routes
nuxt: Allow updating props with
setPageLayoutnuxt: Enable dragging and minimizing for error overlay
nitro,nuxt: Add support for payload extraction in dev
rspack,webpack: Add inline styles
kit: Add forward-compatible nitro types
Performance
nuxt: Do not init layer alias transform when using vite
vite: Add hook filters for ssr styles plugin
vite: Optimize
nuxt:ssr-stylespluginnuxt: Use filter for vfs plugin load
nuxt,vite: Use filters to avoid running hooks unnecessarily
nuxt,vite: Add more filters to internal plugins
Fixes
kit: Normalize local layer paths with trailing slashes
nuxt: Avoid overwriting multiple head input in island handler
nuxt: Update meta instead of calling
router.replacein page hmrnuxt: Don't call
page:loading:endin cache if already calledvite: Add error handling for parsing
NUXT_VITE_NODE_OPTIONSnuxt: Do not skip middleware when
appMiddlewarereferences invalid keynitro: Clipboard copy in error overlay
webpack,rspack: Resolve deep imports in virtual files
webpack: Disable async chunks in dev mode
webpack: Correctly evaluate sourcemap name
nuxt: Handle node10 resolution for
nuxt/metanuxt: Do not early return if component priorities conflict
nuxt: Use
keyfor tag deduplication in<Head>componentschema,vite: Resolve
build.transpilewhen initialising vitenuxt,rspack,webpack: Inject module identifiers for webpack builders
nuxt: Add key to head components for proper deduplication
nitro: Check prettyResponse.body type before error overlay
nuxt: Don't URI-encode static route paths
nuxt: Skip internal stub routes from prerender
kit,schema: Align module
onUpgradearguments with typesnuxt: Handle unsafe number parsing in useCookie decode
nuxt: Do not externalise
rou3nitro: Add
noUncheckedIndexedAccessto server tsconfignuxt: Update global reference to globalThis in
useRequestFetchvite: Configure hmr port for server build
kit: Add forward compatible nitro v3 types
nitro,nuxt: Do not import nitro deps in builders
nitro: Add
h3types to auto-importsschema: Add some more directories to ignore
nitro: Also augment
nuxt/schemanuxt: Make asyncData properties reactive in Options API
nuxt: Rerender
NuxtPagewhen nestedNuxtLayouthas explicitly disabled layoutsnuxt,schema: Clean up types
nuxt: Allow user augmentation of runtime config
kit,nitro: Enable
allowArbitraryExtensionsby defaultnuxt: Decode client-side pathname for non-ASCII route aliases
nuxt: Force remount suspense when navigating after pending
nuxt: Add documentation link to server builder error message
nuxt: Validate placeholder/fallback tags + warn about placeholder/fallback props
nuxt: Force flush
useAsyncDatadebounced execute post watcher flushnitro: Process isr/swr/cache keys
nuxt: Add
typeFromsupport forimports.d.tstemplate exportsnuxt: Ensure we inline styles for
hydrate-nevercomponents
Build
- Removed
Remove babel debugging plugin from jiti stub options
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.