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

24 Jan 2023Where it was published

3.21.11 is the newest release of 3.x.

In short

1 removed25 new2 faster34 fixed2 changed160 internal

  • Removed

    nuxt: Remove deprecated req/res access

Security

12 advisories affect 3.1.0; 4.6.0 fixes the others

7 more

Release note

3.1.0 is the first minor release after Nuxt 3.0 including bug fixes and enhancements.

💬 Release Discussion

Highlights

  • 📖 Lots of improvements to the documentation and website (you can already see them in nuxt.com)

  • 🏝️ Experimental component Islands and server only components

  • ✨ New onNuxtReady, useNuxtData and useSeoMeta composables

  • ﹛ experimental config schema (for module or theme authors)

  • 💪 Upgraded to Nitropack v2

  • ⚡️ Migrated to Vite 4 and Rollup 3.

Changelog

compare changes

Enhancements

  • nuxt: Experimental server component islands

  • nuxt: Add onNuxtReady composable

  • useNuxtData composable

  • nuxt: Support for extending error.vue in layers

  • vite: Upgrade to vite 4

  • nuxt: Deep watch useCookie ref value by default

  • vite: Display production build stats

  • nuxt: Server-only components

  • imports: imports:context hook for unimport context

  • vite: Support build.transpile as function

  • nuxt: Prefetch middleware/layouts + await layout loading

  • nuxt: Support server components with extracted payloads

  • kit: Add extendRouteRules method

  • nuxt: Allow disabling color for <NuxtLoadingIndicator>

  • head: useSeoMeta composable

  • Experimental config schema

Performance

  • nuxt: Use static import of @unhead/ssr

  • nuxt: Add tree-shaken useServerSeoMeta composable

Fixes

  • Remove postcss.config from schema

  • nuxt: Include missing <NuxtPage> component props

  • nuxt: Allow layouts to receive custom props

  • test-utils: Do not hide vitest output

  • nuxt: useCookie with defaults should return non-null value

  • nuxt: Defer render-blocking prefetches until after load

  • nuxt: Speculation rules should be reactive

  • kit: Support applying .nuxtignore within external layers

  • Removed

    nuxt: Remove deprecated req/res access

  • nuxt: Await plugin asyncdata promises in nuxt hook

  • schema: Add hookable dependency

  • vite: Skip only vite transform middleware

  • nuxt: Remove absolute paths from routes objects

  • nuxt: Make dev-only regexp less greedy

  • nuxt: Set is loading state for <NuxtLoadingIndicator> after throttle

  • cli: Show an error if no value is supplied for the --template flag

  • vite: Defer to nitro to copy public dir

  • nuxt: Include components runtime dir in build output

  • nuxt: Add build.transpile strings to nitro inline list

  • nuxt: Support deep assign on empty object for app config

  • nuxt: Don't short circuit middleware after validate function

  • nuxt: Don't try to override computed layouts in definePageMeta

  • nuxt: Allow overriding lower layer composables

  • nuxt: Update class prop type for head components

  • nuxt: Avoid injecting url helpers into globalThis

  • nuxt: Name anonymous components in render tree

  • vite: Add additional before skipping vite transform

  • kit: Resolve group syntax of ignore

  • nuxt: Use query for hashing the fetch key

  • cli: Prevent showing stack traces while scaffolding

  • nuxt: Provide types for modules as array

  • vite: Don't skip loading styles in hydration phase

  • vite: Enable css sourcemaps in dev based on sourcemap

  • nuxt: Await async callWithNuxt calls

  • nuxt: Let router handle internal redirects within middleware

  • nuxt: Import onServerPrefetch

  • Upgrade unimport, close #15594

  • Upgrade unimport

Styles

  • Lint docs

  • Split out type imports

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.