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
Your version

4.6.3

27 Oct 2026Where it was published

4.6.4 is the newest release of 4.x.

Summary· from the note as AI read it

Security fixUpgrade: this release fixes a security issue.

Before you upgrade

  • Check code relying on navigateTo returning RouteLocationRaw type.To check
  • Check route rules with case-dependent constraints using sensitive: false.To check

Security

  • Upgrade to stop dev server reading files named in client error reports.
  • Upgrade to block dev server access to nitro dev output.
  • Upgrade to prevent generated app secret being served in dev.
  • Upgrade to fix dot-segment path handling in request paths.
  • Upgrade so redirect route rules apply to page islands.

New

  • nitro,nuxt,rspack,webpack: bundle esm vue + reuse caches
  • nuxt: server render internal custom links without RouterLink
  • nuxt: skip unneeded typed routes generation

In short

2 breaking5 security3 faster16 fixed17 internal

  • Breaking

    nuxt: hide RouteLocationRaw from navigateTo's public return type

    To check
  • Breaking

    nuxt: reject case-dependent route rule constraints w/ sensitive: false

    To check

Security

Fixes 1 advisory that affected 4.6.2

Release note

The section about nuxt of a note shared by several packages.

v4.6.3 is the next patch release.

Changelog

compare changes

Security fixes

Performance

  • nitro,nuxt,rspack,webpack: bundle esm vue + reuse caches

  • nuxt: server render internal custom links without RouterLink

  • nuxt: skip unneeded typed routes generation

Fixes

  • nuxt: defer app scope cleanup on external navigation

  • nuxt: prevent useCookie CookieStore sync from rewriting with refresh

  • nuxt: only return redirects from navigateTo while middleware runs

  • nuxt: remove purged entries from _asyncData

  • nuxt: hide RouteLocationRaw from navigateTo's public return type

  • nuxt: tree-shake auto-imported #app composables

  • nuxt: don't treat constrained route rules as covering dynamic pages

  • nuxt: include shared/ in build cache hash

  • nuxt: hash keyed function ids + page import names relative to rootDir

  • nuxt: encode page paths before matching route rule keys

  • nuxt: handle rejected updateCallbackDone of aborted view transition

  • nuxt: reject case-dependent route rule constraints w/ sensitive: false

  • nuxt: don't case-fold regex constraints in route rule keys

  • nuxt: normalise page prefix when finding route rule exceptions

  • nuxt: avoid self-referencing nuxt/schema augmentation

  • nuxt: let nightly runtime resolve its own nuxt/* imports

  • nuxt: don't warn for vite+ vite.config files

  • nuxt: clamp numeric v-for sources in island renders at render time

  • deps: update nitropack to 2.13.5 + drop obsolete workarounds

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.