nuxt

4.5.0 is the next minor release.

📣 Some News

Preparing for Nuxt 5

A good chunk of this release is (hopefully) invisible plumbing for Nuxt 5. We've moved onto the latest major versions of several core dependencies (unhead v3, unctx v3, and Vite 8), switched the framework's own build over to tsdown, and introduced a stable nuxt/* build output contract with dev exports so that type-checking in the Nuxt monorepo works without a build step (#35463, #35605).

Much of this is working to shrink the gap between v4 and v5 internally, so that the migration will be as boring as possible.

With the release of Nuxt v4.5, our focus as a team will turn to stabilising Nuxt v5 and creating compatibility utilities to make the upgrade as smooth as possible.

Nuxt 3 End-of-Life

Nuxt 3 reaches end-of-life on July 31, 2026, so this is one of the last few 3.x releases we'll ship. If you're still on v3, now is a great time to move across. Most people told us the v3 to v4 upgrade was smooth, and we've kept the upgrade guide up to date.

Alongside v4.5.0 we're publishing a maintenance patch for the 3.x line (v3.21.9) with the compatible bug fixes and smaller improvements from this release backported. The headline items here (Vite 8, Rspack 2, unhead v3, unctx v3) are major upgrades and stay v4-only, so 3.x remains stable as it approaches end-of-life.

👀 Highlights

Nuxt 4.5 is a big one. This release ships three major upgrades to the build layer (Vite 8, Rspack 2, and a brand new Rsbuild-powered pipeline for the Rspack builder), an experimental SSR streaming mode, a handful of new composables and conventions, and a lot of groundwork that brings us closer to Nuxt 5.

There's a lot here, so grab a coffee. ☕️

⚡️ Vite 8

Nuxt now runs on Vite 8 (#34256). This brings faster cold starts, the latest Rolldown-powered internals, and many upstream improvements from the Vite team.

For most apps this is a transparent upgrade. If you have custom Vite plugins or config, it's worth skimming the Vite migration guide to check for anything that affects you.

🦀 Rspack 2 and Rsbuild

If you use the Rspack builder, this release is a substantial upgrade. We've moved to Rspack 2 (#34929), which is faster and lighter, and rebuilt the builder on top of @rsbuild/core (#35489).

The public surface stays the same. You still opt in with builder: 'rspack' and the existing rspack:* hooks continue to work:

// nuxt.config.ts
export default defineNuxtConfig({
  builder: 'rspack',
})

Under the hood, though, a lot has changed for the better:

• The dev server now runs in middleware mode via Rsbuild, replacing webpack-dev-middleware and webpack-hot-middleware (#35575).
• We use an Rspack-specific Vue loader for correct SSR scoped-style ids and stricter ESM resolution (#35566).

🌊 Experimental SSR Streaming

This is one I'm particularly excited about. You can now enable SSR streaming to dramatically improve Time to First Byte (#34411). Instead of buffering the whole rendered page and sending it in one go, Nuxt flushes the HTML shell (your <head>, styles, preload hints, and entry scripts) immediately, then streams the body as Vue renders it.

// nuxt.config.ts
export default defineNuxtConfig({
  experimental: {
    ssrStreaming: true,
  },
})

Streaming is automatically disabled for bots and crawlers so search engines still receive fully-rendered HTML. You can tune which user agents count as crawlers, and you can opt individual routes out:

// nuxt.config.ts
export default defineNuxtConfig({
  experimental: {
    ssrStreaming: {
      botRegex: /googlebot|bingbot|my-internal-crawler/i,
    },
  },
  routeRules: {
    '/no-stream/**': { streaming: false },
  },
})

There's one thing worth understanding before you turn it on. Because streaming commits the HTTP status and headers with the very first byte, anything that mutates the response after rendering has begun (a setResponseStatus() in a <script setup>, a cookie write during middleware, and so on) can't reach the client. Nuxt handles the common cases for you: routes with redirect, cache, isr, swr, noScripts, or ssr: false rules automatically fall back to the buffered renderer, and in development we log a warning naming any dropped mutations so nothing fails silently.

📖 SSR streaming documentation

🩺 Stable Error Codes

This one I'm really happy about. Nuxt now has a stable error code system (#35429). Warnings and errors raised during build and at runtime now carry a stable code (like NUXT_E1001 or NUXT_B5001), a short explanation of why it happened, and a concrete fix to try.

Every code is greppable and bookmarkable, and the ones that need more than a one-line fix link straight to a dedicated docs page. For example, the classic "a composable was called outside a Nuxt context" now surfaces as NUXT_E1001 with the why/fix inline and a docs page explaining the context rules and how to use runWithContext().

To keep production output lean, the verbose why/fix text is stripped from production builds, leaving just the stable code.

This is the foundation for much better error messages across Nuxt, and we'll keep migrating existing warnings and errors onto it over the coming releases. If you've ever squinted at a cryptic Nuxt message, this is for you.

🎨 useLayout Composable

There's a new useLayout composable for reading the layout that's been resolved for the current route (#35623). Previously there was no clean, reactive way to ask "which layout is this page using?" from within a component.

<!-- app/components/LayoutBadge.vue -->
<script setup lang="ts">
const layout = useLayout()
</script>

<template>
  <span>Current layout: {{ layout }}</span>
</template>

It returns a read-only computed ref, so it stays in sync as you navigate or as route rules and definePageMeta change the resolved layout.

📖 useLayout documentation

🪟 Named Views

Nuxt now supports named views through a filename convention (#35123). If a parent page renders more than one <NuxtPage> outlet, you can give each outlet a name and provide a sibling page file for it using the name@view.vue convention:

# Directory Structure
-| pages/
---| parent/
-----| child.vue
-----| child@sidebar.vue
---| parent.vue

<!-- pages/parent.vue -->
<template>
  <div>
    <NuxtPage />
    <aside>
      <NuxtPage name="sidebar" />
    </aside>
  </div>
</template>

Navigating to /parent/child renders child.vue into the default outlet and child@sidebar.vue into the sidebar outlet. This has actually been possible in Vue Router for a long time; this release wires it up to Nuxt's file-based routing.

📖 Named views documentation

🚦 enabled Option for useFetch and useAsyncData

You can now gate data fetching with a reactive enabled option (#33260). While enabled is false, every execution is blocked (the initial fetch, execute/refresh, and watch triggers), and if you flip it from true to false mid-flight, the in-flight request is cancelled without clearing your existing data.

<script setup lang="ts">
const query = ref('')

const { data } = await useFetch('/api/search', {
  query: { q: query },
  // Only fetch once the user has typed something
  enabled: () => query.value.length > 2,
})
</script>

This is perfect for dependent or conditional queries, where you don't want to fire a request until some precondition is met. It pairs naturally with a getter or a ref, so it stays reactive.

📖 useAsyncData documentation

🔗 NuxtLink Prefetch Control for Custom Slots

When you use <NuxtLink> with the custom prop, Nuxt no longer attaches prefetch handlers for you, because it can't know how you've structured your markup. To make that ergonomic, the slot now exposes everything you need to wire prefetching up yourself (#34539):

<template>
  <NuxtLink
    v-slot="{ href, navigate, prefetch, prefetched, shouldPrefetch }"
    to="/about"
    custom
  >
    <a
      :href="href"
      :class="{ 'is-prefetched': prefetched }"
      @click="navigate"
      @pointerenter="shouldPrefetch('interaction') && prefetch()"
      @focus="shouldPrefetch('interaction') && prefetch()"
    >
      About page
    </a>
  </NuxtLink>
</template>

You get prefetch to trigger it, prefetched to know whether it's already happened (great for a prefetched class), and shouldPrefetch to respect the user's connection and config.

📖 NuxtLink documentation

⚡️ Forwarded Preload Hints on Prefetch

Here's another one we'd love you to try. When you prefetch a link to a route with payload extraction, Nuxt already primes the destination's data and chunks. With the new opt-in experimental.prefetchPreloadTags (#35144), it also forwards the destination's <link rel="preload"> and modulepreload hints (whatever the page sets via useHead, or via modules like @nuxt/image's <NuxtImg preload>) into the current document, downgraded to rel="prefetch" so they don't compete with the resources the user is looking at right now.

// nuxt.config.ts
export default defineNuxtConfig({
  experimental: {
    prefetchPreloadTags: true,
  },
})

The practical effect is that heavy above-the-fold assets on the next page (a hero image, a critical script) start downloading while the user is still on the current one, so the navigation feels instant. It's off by default while we gather feedback, so please give it a spin and tell us how it behaves on your app.

🌐 import.meta.envName

The resolved Nuxt environment name is now available at runtime as import.meta.envName for both Vite and webpack/Rspack builds (#34844). This is the value set by --envName (or the resolved default), so you can branch on it in your app code:

if (import.meta.envName === 'staging') {
  // enable staging-only behaviour
}

📖 import.meta documentation

🔭 Tracing Channels for SSR Events

Nuxt now publishes diagnostics-channel traces for its server-side subsystems (#35191). It's unopinionated: we emit nuxt.render, nuxt.island, nuxt.data, and nuxt.plugin channels following the untracing naming convention, and you can build OpenTelemetry (or anything else) on top. It works in Node, Deno, Bun, and Cloudflare Workers.

// nuxt.config.ts
export default defineNuxtConfig({
  // Turn on Nuxt's own channels
  tracingChannel: true,
})

You can also enable it granularly. In Nuxt v5, there will be additional Nitro-level channels:

// nuxt.config.ts
export default defineNuxtConfig({
  tracingChannel: {
    nuxt: true,
  },
})

📦 Dependency Upgrades

unhead v3

Nuxt's head management now runs on unhead v3 (#34793). It's smaller, uses a synchronous engine internally, and ships better type-safety for useHead out of the box. This also unblocks SSR streaming.

unctx v3

We've moved to unctx v3 (#35541), which resolves a class of long-standing async context issues (#33644). This is part of the composable-context reliability work that continues into v5.

And more

We've also updated magic-string to v1, Babel to v8, and pulled in the latest Rolldown across the board. Running nuxt upgrade --dedupe (see below) is the easiest way to pull these through cleanly.

🛠️ Nuxt CLI

This release bundles some improvements from @nuxt/cli v3.36 and v3.37:

• nuxt module remove to uninstall a module and clean up its config (nuxt/cli#1306), the natural companion to nuxt module add.

• Non-interactive nuxt init for scripting and CI (nuxt/cli#1341), plus it now respects the template's own package manager instead of prompting (nuxt/cli#1330).

• Type-check onboarding: nuxt typecheck now offers to install vue-tsc and typescript for you if they're missing (nuxt/cli#1316).

• Golar support for type-checking: nuxt typecheck can now use Golar as an alternative to vue-tsc (nuxt/cli#1362). It's picked up automatically if it's installed (or a golar.config.* file exists), and you can force a checker with --checker=vue-tsc or --checker=golar:

  nuxt typecheck --checker=golar
  

• Layer-aware dev server: the dev server now reloads on changes to local layer nuxt.config files (nuxt/cli#1345).

🧩 TypeScript Plugin and Named Layout Slots

Nuxt's experimental TypeScript plugin is powered by @dxup/nuxt, and this release bundles a newer version of it. If you haven't tried it, turning on experimental.typescriptPlugin gives you a set of editor niceties: renaming an auto-imported component updates every usage, plus go-to-definition for glob imports, Nitro routes, definePageMeta, runtimeConfig, and typed route names.

New in the bundled version is an opt-in runtime feature: named layout slots (KazariEX/dxup#20). You can write a top-level named-slot template in a page and have it forwarded into the matching named slot of the active layout. That lets a page inject content into its layout's slots, which file-based layouts don't otherwise allow.

Enable it alongside the plugin:

// nuxt.config.ts
export default defineNuxtConfig({
  experimental: {
    typescriptPlugin: true,
  },
  dxup: {
    features: {
      namedLayoutSlots: true,
    },
  },
})

Then a layout can expose named slots:

<!-- layouts/center.vue -->
<template>
  <slot />
  <slot name="side" one="one" />
</template>

And any page using that layout can fill them:

<!-- pages/about.vue -->
<script setup lang="ts">
definePageMeta({ layout: 'center' })
</script>

<template>
  <template #side="{ one }">
    This "{{ one }}" comes from the layout slot.
  </template>
  <div>About page</div>
</template>

📖 typescriptPlugin documentation

🔥 Performance and Reliability

As always, a lot of work has gone into making Nuxt faster and steadier.

One you can opt into today is the shared file watcher (#35143). Vite already runs a chokidar-based watcher, so Nuxt can piggy-back on it instead of spinning up a second one, using less memory and fewer file handles. This becomes the default with compatibilityVersion: 5, but you can turn it on now and let us know how it goes:

// nuxt.config.ts
export default defineNuxtConfig({
  experimental: {
    watcher: 'builder',
  },
})

There are also some other good performance improvements that don't need to be opted into:

• Faster dev startup: dev-only Nitro and pages work is now deferred and streamlined (#35381, #35383).
• Leaner production builds: the island-renderer chunk is skipped entirely when you use no islands (#35456), and plugin handling is tree-shaken out of prod builds (#35278).
• Improved island hashing: more stable island and key hashing, with getIslandHash and hashKey now exposed (#35583).
• Concurrency and I/O wins across Kit path resolution and Nitro inline styles (#35511, #35514).

A couple of other nice quality-of-life fixes:

• $fetch is now auto-imported in user code, which fixes edge cases with top-level $fetch.create under Rolldown's output format (#35581).
• Nuxt now honours system HTTP_PROXY / HTTPS_PROXY environment variables in the builder environment (#35183).
• HMR now works for defineNuxtComponent in JSX (#35620).

⚠️ Heads-Up Before Upgrading

As mentioned above, this release includes three major dependency bumps. For most apps they're transparent, but they're worth a moment of attention:

• Vite 8: check custom Vite plugins and config against the Vite migration guide.
• Rspack 2: if you use builder: 'rspack', the internals are now Rsbuild-based, so custom Rspack config may need review.
• unhead v3: possible breaking type changes from stricter useHead typing.

⬆️ Upgrading

Our recommendation for upgrading is to run:

npx nuxt upgrade --dedupe

# or, if you are staying on the 3.x line
npx nuxt@latest upgrade --dedupe --channel=v3

This will deduplicate your lockfile and help ensure you pull in updates from the other dependencies Nuxt relies on, particularly across the unjs ecosystem (which matters more than usual this release, given the major bumps).

Thank you to all of the many contributors to this release. This was a big one, and it wouldn't happen without you. 💚

👉 Changelog

compare changes

🚀 Enhancements

• rspack: Upgrade to rspack v2 (#34929)
• nuxt: Migrate to unhead v3 (#34793)
• nuxt: Support named views via filename convention (#35123)
• nuxt: Expose environment name on import.meta (#34844)
• nuxt: Forward destination preload hints on link prefetch (#35144)
• nuxt: Honour http proxy env vars in builder environment (#35183)
• kit: Support allowImportingTsExtensions (87c214b34)
• nitro,nuxt,schema: Add experimental SSR streaming (5f4efe5a5)
• vite: Migrate to Vite 8 (#34256)
• nitro,nuxt: Add support for tracing channels for ssr events (#35191)
• kit,nitro,nuxt,schema,vite,webpack: nuxt/* build output contract (#35463)
• nuxt: Expose NuxtLink prefetch props for custom slot (#34539)
• rspack: Use rspack-specific Vue loader (a085e8e34)
• rspack: Use rspack-specific Vue loader (#35566)
• nuxt,vite: Attach vite HMR to the shared dev server listener (a8ea0c7e2)
• nuxt: Add option to AsyncData ()

🔥 Performance

• nuxt,vite: Reuse vite watcher via experimental.watcher (#35143)
• nuxt: Tree-shake unneeded plugin handling from prod builds (#35278)
• nuxt: Defer dev-only nitro startup work (#35381)
• nuxt: Reduce dev pages startup work (#35383)
• vite: Skip unnecessary decorator transforms (#35395)
• nuxt,rspack,vite,webpack: Migrate to rolldown-string (#35058)
• nitro,nuxt,vite: Remove unused dependencies (#34861)
• nuxt: Re-parse transformed file once in tree-shake plugin (#35509)
• nuxt: Index scanned components by name to avoid quadratic lookup (#35510)
• kit: Stat paths directly and probe extensions in parallel (#35511)
• nitro: Load inline style chunks concurrently (#35514)
• nuxt: Skip island-renderer chunk when no islands used (#35456)

🩹 Fixes

• nuxt: Fix explicit return types of factory types (40a80ec7d)
• vite: Do not await ready event for vite watcher (6fe539f52)
• vite: Invalidate modules for legacy vite server (#35315)
• kit,nuxt: Pass error as cause when we re-throw (#35387)
• nuxt: Make virtual module IDs stable across hosts (#35317)
• vite: Inline CSS for lazy components imported from #components (#35215)
• nuxt: Validate <ClientOnly> fallback tag name (#35325)
• vite: Extract server page CSS when inlineStyles is disabled (#35209)
• nitro: Include nested layers in nitro transforms (#35327)
• kit: Don't exclude layer module runtime files from app tsconfig (#35326)
• nitro: Export empty styles object with ssr: false (#35330)
• nuxt: Emit auto-import paths as files, not directories (#35333)
• nuxt: Suppress spurious slot warning in NuxtPage during nav (#35335)
• vite: Preserve backslash separators in windows named pipe path (#35336)
• nuxt: Detach in-flight promise on useAsyncData teardown ()

💅 Refactors

• nitro,nuxt: Add explicit return types to runtime files (#35139)
• nuxt: Resolve builder earlier + skip watcher for nuxt prepare (#35141)
• nuxt: Delete cleared keys in clearNuxtData & clearNuxtState (#35142)
• nuxt: Use jiti fsCache instead of deprecated cache (#35268)
• nitro: Use walkResolver instead of deprecated resolveUnrefHeadInput (#35267)
• nuxt: Add type predicates (#35208)
• vite: Type vite-node-runner error data and resolve #vite-node types from source (#35334)
• nuxt: Split head runtime plugin by environment (#35389)
• nuxt: Use rolldown/utils instead of oxc-* dependencies (#34983)
• kit,vite,webpack,nitro,schema: ssrStyles build output => lazy code provider (#35601)
• nuxt,nitro: Use dev exports for no-build type-checking (#35605)
• rspack: Use rsbuild to power rspack builder (#35489)
• vite: Extract TemplateHMRPlugin from DevServerPlugin (#35579)

📖 Documentation

• Add builder guide (#35576)
• Correct and improve useAsyncData and useFetch (#35528)
• Improving testing documentation for better understanding (#35526)
• Fix incorrect transform signature in useAsyncData/useFetch type docs (#35403)
• Add minimal version badges to API documentation (#34485)
• Clarify usage of await with useFetch (#33745)
• Add badges for new features (1839fe01d)
• Remove enabled from useFetch docs (bf7810600)
• Add tip about prerendering registration for pages (#35635)
• Clarify that useFetch keys are unique per call site (#35645)
• Clarify useFetch custom data error (#35647)

📦 Build

• Use tsdown to build project (#35179)

🏡 Chore

• Update lockfile (92087005f)
• Handle cleaning nuxt build dist manually (aaafe9879)
• Upgrade oxc/tsdown/rolldown deps together (28173926d)
• Use vp in nightly release script (97b56d98d)
• Update lockfile for tsdown build and dev exports (5d9cd2d67)
• Update bundle size snapshots (b9d353516)
• Allow node version updates (#35297)
• Update bundle size (d37b13b60)

✅ Tests

• Strip host path from server bundle before measuring size (#35316)
• Run playwright tests in dev mode too (#35329)
• nuxt: Benchmark dev loadNuxt startup (#35382)
• Update bundle size snapshot (64a834281)
• Use h3 v1 syntax in test (1ea2eec07)
• Use experimental.attachDebugInfo (7c2397ae6)
• Update assertions (55f7ea025)
• Pack with pnpm before running attw to honour publishConfig (e2f0dd69d)
• Reduce flakiness on hydration tests (#35457)
• Improve test stability on macos (#35462)
• Force disable test mode for bundle size tests (#35558)
• Pin typescript in basic-types fixture to dedupe vue (a3b824918)
• webpack: Cover Vue loader scope hashes (824daffa0)
• builders: Clean up Vue loader fixtures (ca18affc3)
• Reenable webpack/rspack dev tests (#35571)
• Await expectNoClientErrors (9f3123f60)
• Mark tests as succeeding for rspack/webpack (513ad306e)
• Add support for non-ascii filenames in public assets (#35636)

🤖 CI

• Reenable bundle size tests 😱 (#35279)
• Only run workflow in nuxt org (#35377)
• Skip entire job, not just step (#35378)
• Error handling for webhook triggers (#35379)
• Update agentscan (#35397)
• Only run benchmark tests in Nuxt org (#35414)
• Don't auto-close team prs 🫣 (cd965f569)
• Use vite-plus to manage pnpm (#35570)
• Use parallel keyword for concurrent workflow steps (#35448)
• Handle missing base branch (for stacked prs) (8d3daa34e)
• Unlink issues from autoclosed PRs (#35615)

❤️ Contributors

• Jordan Labrosse (@Jorgagu)
• Luke Nelson (@luc122c)
• Florian Heuberger (@Flo0806)
• Daniel Roe (@danielroe)
• Yannik Schröder (@yschroe)
• Mateleo (@Mateleo)
• Matej Černý (@cernymatej)
• Eduardo San Martin Morote (@posva)
• Darlan José Batista do Prado (@DarlanPrado)
• Ulrich-Matthias Schäfer (@Fuzzyma)
• Bochkarev Ivan (@Ibochkarev)
• Julien Huang (@huang-julien)
• Damian Głowala (@DamianGlowala)
• KazariAI (@KazariAI)
• Fahad Khan (@oniChan1226)
• skoenfaelt (@skoenfaelt)
• Cynthia Rey (@cyyynthia)
• meomking (@CaptainWang98)
• antlis (@antlis)
• Néstor (@Nsttt)
• Issayah (@VividLemon)
• Alexander Lichter (@TheAlexLichter)
• Anoesj Sadraee (@Anoesj)
• Quentin Macq (@quentinmcq)
• raminjafary (@raminjafary)
• Kurt Medley (@HeavyMedl)
• isksss (@isksss)
• Matteo Gabriele (@MatteoGabriele)
• Max (@onmax)
• Harlan Wilton (@harlan-zw)

Auto-generated commit list for the entire repository.

• chore(deps): update all non-major dependencies (4.x) (#34542) (d1694f0)
• chore(deps): update all non-major dependencies (4.x) (#34602) (6fb3b4a)
• chore(deps): update dorny/paths-filter action to v4 (4.x) (#34606) (384d722)
• chore(deps): update devdependency @typescript-eslint/parser to v8.57.1 (4.x) (#34618) (e9b2fa6)
• chore(deps): update devdependency h3-next to v2.0.1-rc.17 [security] (4.x) (#34658) (a977dea)
• docs: add v4.4 badge for layout props (#34528) (79922b3)
• docs: document that component props are sent in query string (619de0d)
• fix(nuxt): handle negative zero in getUserTrace slice boundary (#34524) (06e5057)
• fix(nuxt): signal error state and clear timers in loading indicator cleanup (#34523) (82ab03f)
• fix(nuxt): fix broken hook cleanup in route announcer (#34525) (7483061)
• fix(nuxt): filter `clearNuxtState` key enumeration by useState prefix (#34541) (452b333)
• fix(nuxt): correct `useFetch` `cache` options type (#34551) (c64dbd8)
• fix(nuxt): prevent in-flight requests from overwriting cleared async data (#34553) (d95ecf8)
• fix(nuxt): check response status before parsing payload (#34555) (8b3762e)
• fix(nuxt): handle TS type assertions on member expression callees in keyed functions parser (#34558) (3b20f19)
• fix(nuxt): use comment as client component placeholder (#33466) (9ae1fc5)
• docs: clarify function signature requirement for custom `$fetch` in `createUseFetch` (#34564) (d3c20e1)
• fix(nitro): resolve h3 export path in nitro vfs (#34566) (c7205cc)
• perf(nitro): directly import nuxt package version (#34567) (491bf21)
• fix(nuxt): use factory resolved options everywhere in `useFetch` (#34568) (7444dc0)
• fix(nitro): use hash-based cache for dev payloads (#34569) (51cb176)
• fix(nuxt): await parcel watcher subscription before registering close hook (#34573) (c58e558)
• fix(nuxt): self-remove hydration error guards after first navigation (#34572) (5c8506d)
• fix(nuxt): mark portal properties as configurable (#34574) (7a1ea64)
• fix(nuxt): retry manifest fetch after transient failure (#34570) (35721f0)
• fix(kit): add PackagePreset type to addImportsSources (#34582) (7258799)
• docs: update experimental typedPages documentation (#34580) (df6e53d)
• chore: do not ship `devDependencies` when publishing (8018d65)
• fix(nuxt): avoid any return type from `callHookWith` in `vue:setup` (#34584) (43c8e0d)
• fix(nuxt): strip DevOnly components with attributes in production builds (#34585) (fb6792e)
• chore: remove unused field 🤦 (2a75ac7)
• test: use `toThrow` instead of `toThrowError` (3d3d816)
• fix(nuxt): move parcel watcher debug timer outside subscription loop (#34590) (72615fd)
• fix(nuxt): preserve falsy prop values in `NuxtTime` data attribute serialization (#34600) (ef0b04c)
• fix(nuxt): clear cached rejected promise in `callOnce` (#34614) (243ae34)
• docs: fix page:loading:start description to match implementation (#34617) (7e31ea5)
• fix(nuxt): correct useAsyncData key type (#34599) (0c2c473)
• fix(nitro): set `__buildAssetsURL` before server entry import (#34607) (8d2fe6b)
• perf(vite,webpack): use vfs for manifest + vite node server (#34666) (771cdc0)
• chore: remove explicit copilot instructions (c7237f2)
• fix(nuxt): use consistent `[nuxt]` prefix in console warnings (#34668) (07613e7)
• ci: add bot workflow (#34677) (66c7830)
• fix(vite): remove obsolete `writeDevServer` + handle vite-node precomputed (f8e49b7)
• test: update bundle size (e4b31ef)
• chore(deps): update devdependency h3-next to v2.0.1-rc.18 [security] (4.x) (#34701) (0457959)
• test: reduce matrices in ci (#34703) (80f4438)
• fix(nuxt): update impound protection for `nitro/*` (ac9e25b)
• perf(nuxt): clean-up build hooks + emit gc'd snapshots (#34587) (1ee83c6)
• fix(nuxt,schema): allow disabling clearing build hooks (#34594) (5766921)
• docs: add missing jsdoc strings (ccb53e0)
• ci: fix bot label (967eca8)
• docs: add example for route middleware setup (#34661) (b59ea93)
• fix(rspack,webpack): emit `styles.mjs` when inline styles off (#34697) (9e5dbd2)
• fix(nuxt): fix FormData body hashing in `useFetch` deduplication key (#34546) (855704e)
• fix(nuxt): generate type re-exports for shared type-only imports (#34632) (f78c637)
• ci: add agent-scan workflow (#34681) (c57213d)
• chore: use single renovate PR for `3.x` and `4.x` branches (1dda87b)
• chore: use top level `vulnerabilityAlerts` config (39999b7)
• chore: dedupe security update prs after update (4734db9)
• ci: correct renovate bot name in workflow (#34708) (cc65416)
• ci: correct dependabot bot name in workflow (#34709) (cf48677)
• chore: throttle per host to reduce rate limits in link checking (#34488) (37f6e0f)
• ci: drop stackblitz link issue commenter (1e9caca)
• fix(nuxt,nitro): add `Symbol` serialization for dev server logs (#34575) (6172d10)
• perf(nuxt): skip key watcher when useAsyncData key is static (#34620) (57eeae8)
• fix(vite): do not process css files with decorator transform (#34769) (3a810f7)
• test: add scroll behavior tests for fixed page key with scrollToTop (#34761) (61fc7a2)
• fix(vite): ensure leading slash in `/@fs` URLs for Windows (#34810) (ff42fe2)
• fix(vite): preserve server-origin errors and surface them via Youch (#34820) (1c08594)
• docs: use new object boolean syntax when prefetchOn interaction (#34825) (08c44a5)
• fix(nitro): do not add import condition for ssr resolve conditions (#34739) (f0d60cc)
• fix(nuxt): fix callOnce navigation mode alternating execution (#34718) (1041467)
• fix(schema,rspack,webpack): respect configured `test` option (#34827) (c8cde4f)
• perf(kit): parallelise module load + cache jiti instances (#34842) (6c0595a)
• doc: fix available in version number for NuxtAnnouncer (#34852) (8e53a86)
• docs: remove @nuxt/scripts from core modules roadmap (#34835) (3b08a33)
• fix(nuxt): handle custom cookie serialisation before passing to `cookie-es` (#34711) (8f6b9aa)
• fix(nuxt): link to correct docs page for keyed functions (#34854) (e7c0913)
• fix(nuxt): adjust `setPageLayout` props type to allow passing arrays of objects (#34860) (1acbaed)
• ci: inline actions triggered by labels into triage actions (ee5acd0)
• perf(nuxt): batch-resolve typescript hoist paths with cached base roots (#34862) (4658a9c)
• docs: remove @nuxt/hints from core modules roadmap (#34867) (9ec06ba)
• fix(nuxt,schema): move config type to schema + mark type peerDeps (#34864) (1bd346e)
• fix(nitro): restore 'import' condition for ssr resolve (af7a127)
• chore(deps): update devdependency typescript to v6 (588047d)
• chore(deps): update devdependency srvx to v0.11.13 [security] (4.x) (#34880) (21b9c35)
• test: update deprecated error assertions (a7a3010)
• chore(deps): update actions/github-script action to v9 (4.x) (#34893) (7e245bb)
• chore(deps): update codecov/codecov-action action to v6 (4.x) (#34895) (375401c)
• chore(deps): update all non-major dependencies (4.x) (#34892) (1a3c957)
• chore(deps): update devdependency @eslint/markdown to v8 (4.x) (#34903) (a4e85d1)
• fix(nitro): re-encode `ssrContext.url` to match vue-router (#34902) (a132756)
• chore(deps): update devdependency knip to v6 (4.x) (#34914) (c57ee5b)
• chore: update renovate config (214a72b)
• fix(schema): remove type peerDependencies (#34894) (40df0b8)
• fix(nuxt): propagate unexpected errors from `isDirectorySync` (#34900) (70c25ff)
• fix(nuxt): bridge `@nuxt/schema` augmentations into `nuxt/schema` (#34905) (e3f466d)
• docs: correct URL (#34907) (cee8acd)
• chore: drop redundant `as const` (#34909) (c45dd76)
• chore(deps): update devdependency vitest-environment-nuxt to v2 (4.x) (#34916) (7d4d041)
• chore(deps): update pnpm/action-setup action to v6 (4.x) (#34919) (1dcda3b)
• chore(deps): update devdependency @nuxt/scripts to v1 (main) (#34830) (b7bd51b)
• fix(nuxt): sync `_route` when navigating up the route tree (#34918) (dc4ef95)
• fix(nuxt): skip `<NuxtPage>` cached vnode when its suspense is unmounted (#34899) (b6f9c3b)
• fix(nitro): only recommend payload extraction when `ssr` is enabled (#34924) (d4cf564)
• chore(deps): update all non-major dependencies (4.x) (#34901) (5acd56e)
• fix(nitro): avoid double-decoding of url (3f1a952)
• chore(deps): update all non-major dependencies (4.x) (#34952) (b5d344b)
• ci: update workflows to use renamed type labels (#34933) (59626fd)
• chore: migrate resolutions to `pnpm-workspace.yaml` (4a39b1b)
• fix(nuxt): flatten buffer before filtering promises and fix rendering of content (#34863) (e8c82ab)
• fix(nuxt): correct async data type inference when using `transform` with `getCachedData` (#34819) (507d279)
• docs: set `NODE_ENV` to `production` in deployment examples (#34937) (ae0ebdf)
• fix(nuxt): avoid transforming `NuxtTeleportIslandComponent` with nuxt-client directive (#34817) (d3600bf)
• fix(nuxt): resolve layer aliases in css files (#34940) (6bdb1de)
• fix(nuxt): invoke user-supplied error handler when suppressing render errors (#34938) (b03db36)
• v4.4.3 (e177b61)
• v4.4.4 (7f8443d)