Packages

@nuxt/rspack-builder

4.6.4 · 2 Nov 2026MIT590 / weekRepositoryHomepagenpmAtom feed

Upgrading @nuxt/rspack-builder From 4.5.1 to 4.6.4

6 releases in betweenevery note read

Reading releases, release notes and advisories…

  1. 4.5.1yours
  2. 4.5.2
  3. 4.6.0security
  4. 4.6.1
  5. 4.6.2
  6. 4.6.3security
  7. 4.6.4target

Start here

Before you upgrade

Tick each one off as you go
  • Deprecated4.6.0

Security

Release by release

  1. 4.6.4

    2 Nov 20262 fixes
    • Fixed

      rspack,webpack: reject unexpected Host headers in dev middleware

    • Fixed

      nitro,vite: remove windows + virtual dev ssr css links after hydration

  2. 4.6.3

    Security fix27 Oct 20261 new · 3 fixes
  3. 4.6.1 – 4.6.22 releases, nothing new or fixed in the notes

  4. 4.6.0

    Security fix5 Oct 202629 new · 18 fixes
    • Security

      The internal error route is only served to an error render, and can no longer be reached from outside (259058cf4, #36305).

    • Security

      Dev error reports are scoped for remote peers, and the dev error channel is kept out of production builds (#36389, #36407).

    • Security

      Unhandled error data is no longer passed to the error page (38a40cfc0), oversized island bodies are drained before being rejected (#36320), and error-render recursion is tracked in request context rather than via a client-controllable header (d8c729435).

    • Deprecated

      schema: deprecate nitro.* options duplicated at the top level

  5. 4.5.2nothing new or fixed in the note

10 other lines we could not sort, mostly version bumps
  • 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 Host checks. Webpack and rspack dev servers now reject requests with an unexpected Host header, as Vite already does. If you use a custom hostname or tunnel, you'll need to add it to the new devServer.allowedHosts option.

    4.6.4
  • workspaceDir detection. When workspaceDir isn't set, Nuxt now only widens it past rootDir to an explicit workspace root or the closest git repository.

    4.6.4
  • Nitropack cached routes. cache, swr and isr route rules now only cache GET and HEAD requests, and no longer store responses that set a cookie or send Cache-Control: private or no-store. Wildcard proxy and redirect rules 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%2Fadmin is covered by a /api/** rule.

    4.6.4
  • 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.config keys 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/server on 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 - /app and /server - and the bundler + server that you ultimately want to build your app.

    4.6.0

188 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.