@nuxt/rspack-builder
4.6.4 · 2 Nov 2026MIT590 / weekRepositoryHomepagenpmAtom feed
Upgrading @nuxt/rspack-builder From 3.21.10 to 4.6.4
28 releases in betweennotes for 26
Reading releases, release notes and advisories…
- 26+
- changes to make
- 0
- advisories fixed
- 113+
- new
- 157+
- fixes
Counted from 26 of 28 release notes. Advisories are counted from the advisory database, in full.
Start here
Before you upgrade
Tick each one off as you go- Breaking4.5.0
- Breaking4.5.0
- Breaking4.3.0
- Breaking4.2.0
- Breaking4.2.0
- Breaking4.2.0
- Breaking4.2.0
- Breaking4.2.0
- Breaking4.1.1
- Breaking4.0.0
Security
- 4.6.3
vite: do not read files named in client error reports (
63299e13c) - GHSA-x287-wcfc-q46c - 4.6.3
vite: deny dev server access to nitro dev output (
c7e204ec6) - GHSA-648h-gw55-m2g7 - 4.6.3
vite: deny serving generated app secret in dev (
16dfdc2a9) - GHSA-3xf4-9g3c-4h4w - 4.6.3
nitro,nuxt: handle dot segments in request paths (
440250d97) - GHSA-9v7c-q64q-vv33 - 4.6.3
nuxt: apply redirect route rules to page islands (
b20372dbe) - GHSA-2fxj-c3j7-rr69 - 4.6.0
- 4.6.0
- 4.6.0
- 4.5.1
If you already upgraded for the earlier route rule advisory (CVE-2026-53721), you still need this release: one of the fixes addresses a regression introduced by that fix.
- 4.5.1
Full details: Nuxt Security Patch Releases and GitHub Security Advisories.
Release by release
- Fixed
rspack,webpack: reject unexpected Host headers in dev middleware
- Fixed
nitro,vite: remove windows + virtual dev ssr css links after hydration
- Fixed
- Security
vite: do not read files named in client error reports (
63299e13c) - GHSA-x287-wcfc-q46c - Security
vite: deny dev server access to nitro dev output (
c7e204ec6) - GHSA-648h-gw55-m2g7 - Security
vite: deny serving generated app secret in dev (
16dfdc2a9) - GHSA-3xf4-9g3c-4h4w - Security
nitro,nuxt: handle dot segments in request paths (
440250d97) - GHSA-9v7c-q64q-vv33
- Security
4.6.1 – 4.6.22 releases, nothing new or fixed in the notes
- Security
- Security
- Security
- Deprecated
schema: deprecate
nitro.*options duplicated at the top level
4.5.2nothing new or fixed in the note
- Security
If you already upgraded for the earlier route rule advisory (CVE-2026-53721), you still need this release: one of the fixes addresses a regression introduced by that fix.
- Security
Full details: Nuxt Security Patch Releases and GitHub Security Advisories.
- New
kit,nuxt,rspack,schema,webpack: Add
.mtsfile extension in resolver - Fixed
rspack,webpack: Resolve loaders and runtime deps from nuxt dirs
- Fixed
nuxt: Remove dev error overlay when error is cleared
- Fixed
rspack,webpack: Resolve bundled postcss defaults from builder
- Security
- Breaking
If you want to test some of the breaking changes of Nuxt v5, you can already opt in with future.compatibilityVersion: 5.
- Breaking
The runtime behaviour is compatible for the vast majority of apps, and promise input (deprecated in v2) is no longer supported.
- New
The dev server now runs in middleware mode via Rsbuild, replacing
webpack-dev-middlewareandwebpack-hot-middleware(#35575). - New
We use an Rspack-specific Vue loader for correct SSR scoped-style ids and stricter ESM resolution (#35566).
- Breaking
- Fixed
vite: Shorter socket name for macOs with tmp fallback
- Fixed
kit: Respect
typeoption infindPath - Fixed
deps: Update nuxt/scripts presets
- Fixed
nuxt: Revert unhead dependency back to v2
- Fixed
28 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. - 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.
668 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.