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

5 Aug 2026Where it was published

4.6.4 is the newest release of 4.x.

In short

4 faster24 fixed29 internal

Security

Release note

4.5.2 is the next patch release.

Changelog

compare changes

Performance

  • nuxt,kit: Skip rewriting unchanged generated files

  • kit,nuxt: Use lazy imports to improve parsing speed

  • vite: Skip html entry probes in bare-import resolver

  • nuxt: Reuse app and component scans for unchanged structures

Fixes

  • vite: Resolve client manifest path from resolved config

  • nuxt: Use client-side navigation for links inside islands

  • nuxt: Generate types for route params defined with definePageMeta

  • nuxt: Serialize island payloads for components with underscores in keys

  • nitro: Dedupe island renders when prerendering

  • nuxt: Drop prefetch hints for never-hydrated chunks

  • vite: Use same asset filenames for worker builds

  • nitro: Reject non-object island props

  • nuxt: Support options api in v-for islands transform

  • nuxt: Improve page meta extraction + performance

  • nuxt: Set build outputs when restoring vue cache

  • kit: Honour nested apply and applyToEnvironment in vite wrapper

  • nuxt: Re-check for preview mode after prerendered page hydration

  • kit,nuxt,vite: Handle missed chokidar watch events

  • nuxt: Settle asyncData status when bailing

  • kit: Clone resolved config with klona rather than klona/full

  • kit: Honour nested plugins' enforce in vite wrapper

  • nuxt: Collect build cache once build outputs are final

  • vite: Resolve vite env api sourcemaps in vite-node

  • nuxt: Don't warn about missing <NuxtPage> on nav + with slot

  • kit: Prepend vite environment wrapper plugin when prepend is set

  • nuxt: Depend on rolldown as a peer to reuse vite's copy

  • nitro: Define import.meta.test for server code

  • nuxt: Match route rules against decoded paths

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.