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 2.15.1 to 4.6.0

133 releases in betweennotes for 127

Reading releases, release notes and advisories…

Other targets from 2.15.1Newest 2.x2.18.1Latest4.6.4
  1. 2.15.1yours
  2. 11 releases
  3. 2.17.0security
  4. 3 releases
  5. 2.17.4security
  6. 2.18.0security
  7. 1 release
  8. 3.0.0major
  9. 30 releases
  10. 3.8.0security
  11. 60 releases
  12. 4.0.0major
  13. 16 releases
  14. 4.4.7security
  15. 2 releases
  16. 4.5.1security
  17. 1 release
  18. 4.6.0target
66+
changes to make
3
advisories fixed
853+
new
1680+
fixes

Counted from 127 of 133 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.2.0
  • Breaking4.2.0
  • Breaking4.2.0
  • Breaking4.2.0
  • Breaking4.2.0
  • Breaking4.1.1
  • Breaking4.0.0
  • Breaking4.0.0

Security

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

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

    4.6.0
  • 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).

    4.6.0
  • 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
  • 4.5.1
  • nuxt: Block path-normalization open redirect in navigateTo

    4.4.7
  • Remove huntr + encourage GitHub vulnerability reporting

    3.8.0
  • Add non-applicable advisory GHSA-3h5v-q93c-6h6q

    2.18.0
  • 2.17.4
  • Mark GHSA-grv7-fg5c-xmjg as not applicable

    2.17.4

Release by release

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

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

  3. 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+

  4. 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).

  5. 4.4.8

    8 Jun 20264 fixes
    • Fixed

      vite: Shorter socket name for macOs with tmp fallback

    • Fixed

      kit: Respect type option in findPath

    • Fixed

      deps: Update nuxt/scripts presets

    • Fixed

      nuxt: Revert unhead dependency back to v2

  6. 4.4.7

    Security fix2 Jun 202629 fixes
    • Security

      nuxt: Block path-normalization open redirect in navigateTo

    • Fixed

      nitro: Assign noSSR before deciding payload extraction

    • Fixed

      vite: Avoid filtering out dirs with shared prefix from allowDirs

    • Fixed

      nuxt: Use resolve from pathe for buildCache path boundary check

  7. 4.4.6

    18 May 20261 new · 19 fixes
    • New

      nitro: Add json extension to payload cache items

    • Fixed

      vite: Use spa entry for vite-node fallback

    • Fixed

      vite: Invalidate SSR module cache when modules are invalidated via plugin hooks

    • Fixed

      nuxt: Match deduplicated resolveComponent calls in jsx blocks

  8. 4.4.5

    10 May 20261 new · 18 fixes
    • New

      kit: Cache layer roots and short-circuit isIgnored relative

    • Fixed

      vite: Resolve vite clientServer with ssr: false

    • Fixed

      nitro: Correct payload route rule for / + override ssr: true

    • Fixed

      nitro: Break recursive rendering deadlocks during prerender

23 other lines we could not sort, mostly version bumps
  • 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
  • All the same features: Route rule layouts, ISR payload extraction, layout props with setPageLayout, #server alias, draggable error overlay, and more

    4.3.0
  • All performance improvements: SSR styles optimization, hook filters, and route rules compilation

    4.3.0
  • Module disabling: Disable layer modules by setting options to false

    4.3.0
  • Critical bug fixes: Async data reactivity in Options API, useCookie number parsing, head component deduplication, and more

    4.3.0
  • Nuxt 2 compatibility has been removed from @nuxt/kit. (This will particularly affect module authors.)

    4.0.0

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