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

3.21.1

7 Feb 2026Where it was published

3.21.11 is the newest release of 3.x.

In short

3 new26 fixed14 internal

Security

18 advisories affect 3.21.1; 4.6.2 fixes the others

13 more

Release note

3.21.1 is a regularly schedule patch release.

Changelog

compare changes

Fixes

  • nuxt: Correct reference format of server builder

  • nuxt: Add status/statusText getters to NuxtError

  • schema: Add direnv and vendor to default ignore

  • nuxt: Focus hash links after navigation

  • nuxt: Exclude head runtime from unhead imports transform

  • kit: Include prereleases in semver satisfy check

  • nuxt: Watch server/ for builder:watch hook

  • nitro: Encode unicode paths in x-nitro-prerender header

  • nitro: Preserve error.message for fatal errors

  • Only enable dynamic imports when ts plugin

  • webpack: Use H3Error for 403 in dev server

  • nuxt: Ensure NuxtError extends Error type

  • vite: Use H3Error for 404 in dev server

  • nuxt: Add backwards compat for #app barrel export in keyed functions

  • nuxt: Track + re-add custom routes on hmr

  • nuxt: Keep vnode when leaving deeper nested route

  • vite: Prevent CSS flickering in dev mode after config changes

  • nuxt: Do not start view transition if there is no route

  • nuxt: Call deferHydration done on NuxtPage unmount

  • nuxt: Handle invalid datetime in <NuxtTime>`

  • nuxt: Preserve middleware error status in 404 fallback

  • nitro: Do not augment nuxt/schema

  • nuxt: Cache manifest files to preserve buildId

  • nuxt: Don't decode query string in SSR context URL

  • nuxt: Allow specifying moduleDependencies by meta.name

  • nuxt: Resolve #components import mapping conflict for packages outside rootDir

  • vite,webpack: Use node.res to send 403/404

  • nitro,nuxt: Align path encoding with vue-router

  • nitro: Augment nuxt/schema once more

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.