v3.14.1

Compare Source

Patch Changes

• #​13168 6b84ec0 Thanks @​jerelmiller! - Fix issue where muting a deprecation from one entrypoint would not mute the warning when checked in a different entrypoint. This caused some rogue deprecation warnings to appear in the console even though the warnings should have been muted.

• #​12970 f91fab5 Thanks @​acemir! - Add a deprecation message for the variableMatcher option in MockLink.

• #​13168 6b84ec0 Thanks @​jerelmiller! - Ensure deprecation warnings are properly silenced in React hooks when globally disabled.

v3.14.0

Compare Source

Minor Changes

• #​12752 8b779b4 Thanks @​jerelmiller! - Add deprecations and warnings to remaining APIs changed in Apollo Client 4.0.

• #​12746 0bcd2f4 Thanks @​jerelmiller! - Add warnings and deprecations for options and methods for all React APIs.

• #​12751 567cad8 Thanks @​jerelmiller! - Add @deprecated tags to all properties returned from any query API (e.g. client.query, observableQuery.refetch, etc.), client.mutate, and client.subscribe that are no longer available in Apollo Client 4.0.

• #​12746 0bcd2f4 Thanks @​jerelmiller! - Add preloadQuery.toPromise(queryRef) as a replacement for queryRef.toPromise(). queryRef.toPromise() has been removed in Apollo Client 4.0 in favor of preloadQuery.toPromise and is now considered deprecated.

• #​12736 ea89440 Thanks @​jerelmiller! - Add deprecations and deprecation warnings for ApolloClient options and methods.

• #​12763 5de6a3d Thanks @​jerelmiller! - Version bump only to release latest as rc.

• #​12459 1c5a031 Thanks @​jerelmiller! - Reset addTypenameTransform and fragments caches when calling cache.gc() only when resetResultCache is true.

• #​12743 92ad409 Thanks @​jerelmiller! - Add deprecations and warnings for addTypename in InMemoryCache and MockedProvider.

• #​12743 92ad409 Thanks @​jerelmiller! - Add deprecations and warnings for canonizeResults.

• #​12751 567cad8 Thanks @​jerelmiller! - Warn when using a standby fetch policy with client.query.

Patch Changes

• #​12750 ecf3de1 Thanks @​phryneas! - Prevent field policies from overwriting/merging into supertype field policies.

v1.4.1

Compare Source

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​eslint/core bumped from ^0.16.0 to ^0.17.0

v1.4.0

Compare Source

Features

• Add config types in @​eslint/core (#​237) (7b6dd37)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​eslint/core bumped from ^0.15.2 to ^0.16.0

v1.3.2

Compare Source

Dependencies

• The following workspace dependencies were updated
  • devDependencies
    • @​eslint/core bumped from ^0.15.1 to ^0.15.2

v1.16.0

Compare Source

   🚀 Features

• Update deps  -  by @​antfu (008ad)

    View changes on GitHub

v1.15.2

Compare Source

   🐞 Bug Fixes

• Prevent race condition of running checker module before eslint config is written  -  by @​sebbayer in #​653 (69aa4)

    View changes on GitHub

v1.15.1

Compare Source

   🐞 Bug Fixes

• Downgrade @eslint/js, fix #​647  -  by @​antfu in #​647 (2c1c1)

    View changes on GitHub

v1.15.0

Compare Source

   🚀 Features

• Relax peer deps range to support ESLint v10, fix #​642  -  by @​antfu in #​642 (305a9)

    View changes on GitHub

v1.14.0

Compare Source

   🚀 Features

• eslint-config: Add no-page-meta-runtime-values  -  by @​danielroe in #​641 (b74a0)

    View changes on GitHub

v1.13.0

Compare Source

   🚀 Features

• Upgrade eslint-flat-config-utils eslint-plugin-import-lite and eslint-plugin-jsdoc  -  by @​antfu (10bf9)

    View changes on GitHub

v1.12.1

Compare Source

No significant changes

    View changes on GitHub

v1.11.0

Compare Source

   🚀 Features

• Allow config key sorting on files not named nuxt.config  -  by @​benedictleejh in #​630 (be2e9)

    View changes on GitHub

v1.10.0

Compare Source

   🚀 Features

• Update deps  -  by @​antfu (23b8b)

   🐞 Bug Fixes

• Update icon path  -  by @​antfu (3f185)

    View changes on GitHub

v1.9.0

Compare Source

   🚀 Features

• Update plugins  -  by @​antfu (b80cb)

   🐞 Bug Fixes

• Add defineNuxtConfig as ESLint's globals, close #​603  -  by @​antfu in #​603 (2e67f)

    View changes on GitHub

v1.8.0

Compare Source

   🚀 Features

• Update plugins  -  by @​antfu (932a7)

    View changes on GitHub

v4.5.0

Compare Source

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.

[!TIP]
If you want to test some of the breaking changes of Nuxt v5, you can already opt in with future.compatibilityVersion: 5. Keep an eye on the Upgrade Guide for details as they land.

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.

[!WARNING]
Vite 8 is a major version bump. If you depend on Vite directly (custom plugins, vite.config tweaks, or ecosystem plugins that pin a Vite version), make sure those are compatible before upgrading in production.

🦀 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).

[!NOTE]
This is the foundation for first-class Rsbuild support. We kept the builder named rspack for now so nothing breaks, but the internals are now Rsbuild all the way down.

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

[!WARNING]
SSR streaming is experimental and off by default. It could be great for content-heavy routes where TTFB matters, but test it against your app's response-mutating logic (status codes, headers, cookies) before shipping it widely. The experimental features docs cover the fallback rules and caveats in detail.

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

[!NOTE]
definePageMeta is read from the default route file only, and per-view rendering modes aren't supported (the parent page's mode applies to the default view).

📖 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 }"
      @&#8203;click="navigate"
      @&#8203;pointerenter="shouldPrefetch('interaction') && prefetch()"
      @&#8203;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,
  },
})

[!NOTE]
Channel names, payload shapes, and option keys may still change while the untracing registry settles.

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

[!WARNING]
unhead v3 introduces type-narrowing for useHead, which can be a breaking type change if you were relying on the looser v2 types. The runtime behaviour is compatible for the vast majority of apps, and promise input (deprecated in v2) is no longer supported. If you hit type errors after upgrading, they're almost always genuine tightening rather than regressions.

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

[!TIP]
Check out our upgrade guide if you're upgrading from an older version.

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 enabled option to AsyncData (#​33260)
• rspack: Use rsbuild dev server in middleware mode (#​35575)
• nuxt: Expose getIslandHash + hashKey + improve hash for keys (#​35583)
• nuxt: Add useLayout composable for accessing the resolved route layout (#​35623)
• nuxt: Support enabled option in useFetch (#​35627)
• Error code system (#​35429)
• nuxt: Require keyed function 'source' with compatibilityVersion 5 (d56662647)
• kit: Order layer aliases before generic root aliases (~, @) (#​35641)
• kit: Add updateAppConfig util for module authors (#​35651)
• nuxt: Warn when parent page lacks NuxtPage (#​35639)

🔥 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 (#​35328)
• nuxt: Respect per-page keepalive set via definePageMeta (#​34526)
• nuxt: Align useFetch error type with runtime (#​35346)
• nuxt: Unwrap getter body in useFetch (#​35343)
• rspack,webpack: Strip invalid webpack PURE annotations (#​35386)
• nuxt: Guard against -1 when unregistering a router hook (#​35391)
• nuxt: Clean up load/error listeners in preloadPayload (#​35392)
• nuxt: Avoid idle wait when refreshing data after hydration (#​35358)
• nuxt: Hash serialized island props (#​35356)
• nuxt: Ensure page:start finishes before page:finish starts (#​35408)
• vite: Invalidate lazily-created SSR modules on render (#​35410)
• nuxt: Preserve plugin navigation during app boot (#​35344)
• vite: Invalidate stale SSR virtual modules on render (#​35413)
• nitro: Don't preload JS for lazy-hydrated components (#​35342)
• vite: Add extension to vite-node-runner virtual specifier (0bf3f1d5d)
• vite: Invalidate ssr copy of regenerated templates (33a581ce7)
• vite: Set define for NODE_ENV and __VUE_PROD_DEVTOOLS__ (#​35444)
• vite: Avoid emitted ssr styles file name collisions (#​35432)
• nuxt: Avoid syncing route too early when reused page remounts (#​35440)
• nuxt: Skip showing route errors for crawlers (#​35411)
• nuxt: Keep nested layout on deferred route during suspended layout switch (#​35443)
• nuxt: Restore deferred query route before page is mounted (#​35442)
• kit,nuxt: Resolve auto-import type paths through shared resolver (#​35451)
• nuxt: Make islands hash backwards-compatible (#​35452)
• vite: Give ssr its own hmr websocket port on vite 8.1 (#​35458)
• nuxt: Auto-import $fetch where possible (#​35581)
• nuxt: Update unctx to v3 (#​35541)
• nitro: Point cache driver at .mjs runtime output (#​35263)
• nuxt: Add head.push for client side (#​35498)
• nitro: Only reload nitro after initial nitro build (30a573733)
• nuxt: Pass nuxt rootDir to typed-router context (#​35565)
• nuxt: Type __nuxt_error marker on NuxtError (06e976d2e)
• kit: noUncheckedSideEffectImports (v5) + disable libReplacement (#​35548)
• nuxt: Node10 compatible subpath exports (a216d732d)
• nuxt: Unwrap module mutation trackers from options after installing (#​35574)
• nuxt: Entity-encode redirect body to preserve query separators (#​35486)
• rspack,webpack: Use async entry in dev to avoid circular import (#​35586)
• nuxt: Tolerate missing dirs in parcel watcher (#​35585)
• nuxt: Respect saved scroll position on same-page back navigation from hash (#​35608)
• nuxt: Resolve unctx helper to an absolute path for server bundling (#​35602)
• nuxt: Apply unctx transform marker through magic-string (#​35618)
• schema: Enable HMR for defineNuxtComponent in JSX (#​35620)
• nuxt: Evict stale forwarded prefetch hints and fix key mismatch (#​35621)
• nuxt: Re-add computeIslandHash for backwards compatibility (353164bb5)
• nitro: Correct nitro runtime config type key (bc3b53add)
• schema: Resolve Vite cache directory from workspace (#​35626)
• nitro: Externalise dev SSR entry to avoid slow rollup re-parse (ff42c54a7)
• nuxt: Drop extension on diagnostics import (c699cc0de)
• nitro: Write prerender cache files atomically (#​35619)
• nitro: Don't import node:process in diagnostics (d73b5df6d)
• nuxt: Apply latest navigation on concurrent navigateTo in built-in router (#​35631)
• nuxt: Update client URL to match SSR on fatal middleware error (#​35637)

💅 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 ([#&#

✂ Note

PR body was truncated to here.