Packages

nuxt

4.6.4 · 2 Nov 2026MIT3.6M / weekRepositoryHomepagenpmAtom feed

The latest release, 4.6.4, is affected by 4 advisories with no fixed version yet.See advisories

Upgrading nuxt From 4.2.2 to 4.6.4

16 releases in betweennotes for 14

Reading releases, release notes and advisories…

  1. 4.2.2yours
  2. 6 releases
  3. 4.4.7security
  4. 1 release
  5. 4.5.0breaking
  6. 4.5.1security
  7. 1 release
  8. 4.6.0security
  9. 2 releases
  10. 4.6.3security
  11. 4.6.4target
4+
changes to make
16
advisories fixed
151+
new
381+
fixes

Counted from 14 of 16 release notes. Advisories are counted from the advisory database, in full.

Start here

Before you upgrade

Tick each one off as you go
  • Breaking4.6.4
  • Breaking4.5.0
  • Breaking4.5.0
  • Deprecated4.6.0

Security

Fixes 16 advisories affecting 4.2.2

Release by release

  1. 4.6.4

    Migration needed2 Nov 20269 fixes
    • Breaking

      nitro,nuxt: require unrouting 0.3.2

    • Fixed

      nuxt: use unambiguous encoding for island hash

    • Fixed

      nuxt: do not expose details of untrusted thrown errors

    • Fixed

      nuxt: strip trailing slashes in linear time

  2. 4.6.3

    Security fix27 Oct 20263 new · 19 fixes
  3. 4.6.2

    16 Oct 202610 fixes
    • Fixed

      nuxt: resolve rooted paths through the URL parser

    • Fixed

      nuxt: resolve empty route types in shared context

    • Fixed

      nuxt: fix scroll offset for IDs starting with numbers

    • Fixed

      nuxt: detect vapor slots with rawVaporSlotKey from vue

  4. 4.6.1

    9 Oct 20268 fixes
    • Fixed

      nuxt: accept any baseURL when fetch response type is named

    • Fixed

      nuxt: allow false in setPageLayout types

    • Fixed

      nuxt: align Serialize object types with JSON

    • Fixed

      nuxt: update publishConfig config export extension

  5. 4.6.0

    Security fix5 Oct 202678 new · 104 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

  6. 4.5.2

    5 Aug 20264 new · 24 fixes
    • New

      nuxt,kit: Skip rewriting unchanged generated files

    • New

      kit,nuxt: Use lazy imports to improve parsing speed

    • New

      vite: Skip html entry probes in bare-import resolver

    • New

      nuxt: Reuse app and component scans for unchanged structures

  7. 4.5.1

    Security fix27 Jul 20266 new · 47 fixes
    • 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
    • New

      nitro: Replace island teleports in a single html pass

    • New

      nuxt: Add vue.optionsApi and disable it for v5+

  8. 4.5.0

    Migration needed18 Jul 202655 new · 63 fixes
    • 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-middleware and webpack-hot-middleware (#35575).

    • New

      We use an Rspack-specific Vue loader for correct SSR scoped-style ids and stricter ESM resolution (#35566).

14 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

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