3.11.2 is the next regularly scheduled patch release.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

👉 Changelog

compare changes

🔥 Performance

• nuxt: Don't tree-shake useServerHead in dev (#26421)
• nuxt: Reduce nuxt island payload (#26569)
• nuxt: Unsubscribe from watch when scope is disposed (#26554)
• nuxt: Reduce router resolutions (#26519)

🩹 Fixes

• nuxt: Handle underscores in island names (#26370)
• nuxt: Don't append new route for redirect if one exists (#26368)
• nuxt: Ignore navigateTo open option on server side (#26392)
• nuxt: Print errors when compiling templates (#26410)
• nuxt: Don't warn about definePageMeta in server pages (#26422)
• nuxt: Pass joinRelativeURL + share paths on server (#26407)
• nuxt: Exclude <srcDir>/index.html from import protection (#26430)
• nuxt: Early return from refreshCookie on server (22ada37b4)
• nuxt: Move v-if to wrapper in islands transform (#26386)
• nuxt: Move directives to client component island wrapper (#26387)
• nuxt: Ignore fetch errors in getLatestManifest (#26486)
• nuxt: Check island element instead of hydration state (#26480)
• nuxt: Add build id to rendered payload url (#26504)
• nuxt: Support serialising rich server logs (#26503)
• nuxt: Handle errors parsing/stringifying logs (4a87c35df)
• nuxt: Augment GlobalComponents in multiple vue modules (#26541)
• nuxt: Suppress warning about resolve cache-driver (#26595)
• nuxt: Handle auto-importing named components (#26556)
• schema: Update webpack transformAssetUrls + pass hoistStatic to vite plugin (#26563)
• schema: Document use case for typescript.shim (#26607)
• nuxt: Normalise rollup opts in island transform w/o nuxt (#26589)
• nuxt: Handle missing Nuxt context in useRoute (#26633)

💅 Refactors

• nuxt: Remove duplicated check (#26544)
• nuxt: Simplify check in navigateTo for server (#26546)
• nuxt: Simplify runtimeConfig initialization of client side (#26558)

📖 Documentation

• Update information about playwright test runner (8e635fd23)
• Add info about dependencies to install (a258bfc34)
• Add missing end block (f55f74798)
• Migration page typo (#26389)
• Advise installing nuxi for debugging with pnpm (#26447)
• Warn about single root element for server components (#26462)
• Adjust grammar (#26482)
• Add contents of the layout in examples (#26532)
• Add note about prerenderRoutes in dynamic routes (#26547)
• Clarify app-config merging strategy note (#26564)
• Update core modules roadmap (#26553)
• Replace process.* with import.meta.* (#26611)
• Correct grammar in typescript.shim JSDoc (#26626)
• Add missing comma (#26644)

🏡 Chore

• Fix typo in test descriptions (#26366)
• Rename to yaml (00018084d)
• Improve pr template (#26562)
• Enable devtools by default in playground (17488508b)
• Migrate to ESLint flat config (#26583)

❤️ Contributors

• Nikita (@nikitadmitr)
• Alex Liu (@Mini-ghost)
• Luke Nelson (@luc122c)
• Damian Głowala (@DamianGlowala)
• Julien Huang (@huang-julien)
• Daniel Roe (@danielroe)
• Antoine Rey (@antoinerey)
• Maxime Pauvert (@maximepvrt)
• Taras Batenkov (@enkot)
• Lehoczky Zoltán (@Lehoczky)
• Pothuraju (@pothuraju-dev)
• xjccc (@xjccc)
• Junaid Ahmed (@junaidkbr)
• Michał Zarach (@michalzaq12)
• Thimo (@ThimoDEV)
• Anthony Fu (@antfu)
• Alexander Lichter (@manniL)
• Serge Doda (@bargel)
• François Rosato (@frosato-dev)

3.11.1 is a patch release addressing regressions in v3.11.0.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

👉 Changelog

compare changes

🩹 Fixes

• nuxt: Ignore console.logs called outside event context (b3ced3d69)
• schema: Include ofetch in typescript.hoist defaults (#26316)
• nuxt: Conditionally use tsx parser (#26314)
• nuxt: Correct finish types and add to docs (0d9c63b82)
• nuxt: Ignore failures to access asyncContext in environments without it (523db1a19)
• nuxt: Handle failure creating BroadcastChannel (#26340)
• nuxt: Don't warn when injecting client-only components (#26341)
• nuxt: Prevent losing pages routes on prerender (#26354)
• nuxt: Pass undefined name when resolving trailing slash (#26358)
• vite: Use ssr result if it exists (#26356)

📖 Documentation

• Fix code block formatting for usePreviewMode (#26303)
• Fix confusing wording (#26301)
• Add note that useId must be used with single root element (401370b3a)
• Mention <DevOnly> component in api section (#26029)
• Note that @nuxt/schema should be used by module authors (#26190)
• Add routeNameSplitter example in migration docs (#25838)

🏡 Chore

• nuxt: Remove unused code (#26319)
• Revert update github/codeql-action action (c72951b06)

🤖 CI

• Configure npm registry in release workflow (68f7d4df8)

❤️ Contributors

• Daniel Roe (@danielroe)
• zunderbolt (@zunderbolt)
• Serge Doda (@bargel)
• Volker Rose (@riddla)
• Turdalin Nurassyl (@trdln)
• Julien Huang (@huang-julien)
• Joaquín Sánchez (@userquin)
• Tanvir Rahman (@Tanvir-rahman)
• Florian Lefebvre (@florian-lefebvre)

👀 Highlights

This is possibly the last minor release before Nuxt v4, and so we've packed it full of features and improvements we hope will delight you! ✨

🪵 Better logging

When developing a Nuxt application and using console.log in your application, you may have noticed that these logs are not displayed in your browser console when refreshing the page (during server-side rendering). This can be frustrating, as it makes it difficult to debug your application. This is now a thing of the past!

Now, when you have server logs associated with a request, they will be bundled up and passed to the client and displayed in your browser console. Asynchronous context is used to track and associate these logs with the request that triggered them. (#25936).

For example, this code:

<script setup>
console.log('Log from index page')

const { data } = await useAsyncData(() => {
  console.log('Log inside useAsyncData')
  return $fetch('/api/test')
})
</script>

will now log to your browser console when you refresh the page:

Log from index page
[ssr] Log inside useAsyncData 
    at pages/index.vue

👉 We also plan to support streaming of subsequent logs to the Nuxt DevTools in future.

We've also added a dev:ssr-logs hook (both in Nuxt and Nitro) which is called on server and client, allowing you to handle them yourself if you want to.

If you encounter any issues with this, it is possible to disable them - or prevent them from logging to your browser console.

export default defineNuxtConfig({
  features: {
    devLogs: false
    // or 'silent' to allow you to handle yourself with `dev:ssr-logs` hook
  },
})

🎨 Preview mode

A new usePreviewMode composable aims to make it simple to use preview mode in your Nuxt app.

const { enabled, state } = usePreviewMode()

When preview mode is enabled, all your data fetching composables, like useAsyncData and useFetch will rerun, meaning any cached data in the payload will be bypassed.

Read more in the docs.

💰 Cache-busting payloads

We now automatically cache-bust your payloads if you haven't disabled Nuxt's app manifest, meaning you shouldn't be stuck with outdated data after a deployment.

👮‍♂️ Middleware routeRules

It's now possible to define middleware for page paths within the Vue app part of your application (that is, not your Nitro routes) (#25841).

export default defineNuxtConfig({
  routeRules: {
    '/admin/**': {
      // or appMiddleware: 'auth'
      appMiddleware: ['auth']
    },
    '/admin/login': {
      // You can 'turn off' middleware that would otherwise run for a page
      appMiddleware: {
        auth: false
      }
    },
  },
})

⌫ New clear data fetching utility

Now, useAsyncData and useFetch expose a clear utility. This is a function that can be used to set data to undefined, set error to null, set pending to false, set status to idle, and mark any currently pending requests as cancelled. (#26259)

<script setup lang="ts">
const { data, clear } = await useFetch('/api/test')

const route = useRoute()
watch(() => route.path, (path) => {
  if (path === '/') clear()
})
</script>

🕳️ New #teleports target

Nuxt now includes a new <div id="teleports"></div> element in your app within your <body> tag. It supports server-side teleports, meaning you can do this safely on the server:

<template>
  <Teleport to="#teleports">
    <span>
      Something
    </span>
  </Teleport>
</template>

🚦 Loading indicator and transition controls

It's now possible to set custom timings for hiding the loading indicator, and forcing the finish() method if needed (#25932).

There's also a new page:view-transition:start hook for hooking into the View Transitions API (#26045) if you have that feature enabled.

🛍️ Server- and client-only pages

This release sees server- and client-only pages land in Nuxt! You can now add a .server.vue or .client.vue suffix to a page to get automatic handling of it.

Client-only pages will render entirely on the client-side, and skip server-rendering entirely, just as if the entire page was wrapped in <ClientOnly>. Use this responsibly. The flash of load on the client-side can be a bad user experience so make sure you really need to avoid server-side loading. Also consider using <ClientOnly> with a fallback slot to render a skeleton loader (#25037).

⚗️ Server-only pages are even more useful because they enable you to integrate fully-server rendered HTML within client-side navigation. They will even be prefetched when links to them are in the viewport - so you will get instantaneous loading (#24954).

🤠 Server component bonanza

When you are using server components, you can now use the nuxt-client attribute anywhere within your tree (#25479).

export default defineNuxtConfig({
  experimental: {
    componentIslands: {
      selectiveClient: 'deep'
    }
  },
})

You can listen to an @error event from server components that will be triggered if there is any issue loading the component (#25798).

Finally, server-only components are now smartly enabled when you have a server-only component or a server-only page within your project or any of its layers (#26223).

🔥 Performance improvements

We've shipped a number of performance improvements, including only updating changed virtual templates (#26250), using a 'layered' prerender cache (#26104) that falls back to filesystem instead of keeping everything in memory when prerendering - and lots of other examples.

📂 Public assets handling

We have shipped a reimplementation of Vite's public asset handling, meaning that public assets in your public/ directory or your layer directories are now resolved entirely by Nuxt (#26163), so if you have added nitro.publicAssets directories with a custom prefix, these will now work.

📦 Chunk naming

We have changed the default _nuxt/[name].[hash].js file name pattern for your JS chunks. Now, we default to _nuxt/[hash].js. This is to avoid false positives by ad blockers triggering off your component or chunk names, which can be a very difficult issue to debug. (#26203)

You can easily configure this to revert to previous behaviour if you wish:

export default defineNuxtConfig({
  vite: {
    $client: {
      build: {
        rollupOptions: {
          output: {
            chunkFileNames: '_nuxt/[name].[hash].js',
            entryFileNames: '_nuxt/[name].[hash].js'
          }
        }
      }
    }
  },
})

💪 Type fixes

Previously users with shamefully-hoist=false may have encountered issues with types not being resolved or working correctly. You may also have encountered problems with excessive type instantiation.

We now try to tell TypeScript about certain key types so they can be resolved even if deeply nested (#26158).

There are a whole raft of other type fixes, including some regarding import types (#26218 and #25965) and module typings (#25548).

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

👉 Changelog

compare changes

🚀 Enhancements

• nuxt: Server-only pages (#24954)
• nuxt: Client-only pages (#25037)
• nuxt: Allow using nuxt-client in all components (#25479)
• nuxt: Add page:view-transition:start hook (#26045)
• nuxt: Custom loading reset/hide delay + force finish() (#25932)
• nuxt: Emit error if <NuxtIsland> can't fetch island (#25798)
• nuxt: usePreviewMode composable (#21705)
• nuxt: Support async transforms for data composables (#26154)
• nuxt: Add dedicated #teleports element for ssr teleports (#25043)
• nuxt: Enable islands if server pages/components present (#26223)
• nuxt: Allow generating metadata for nuxt components (#26204)
• vite: Handle multiple/custom public dirs (#26163)
• ...

3.10.3 is a regularly-scheduled patch release.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the vue and unjs ecosystems.

👉 Changelog

compare changes

🩹 Fixes

• nuxt: Respect dedupe option in useFetch (#25815)
• nuxt: Bypass browser cache when fetching app build id (#25813)
• nuxt: In dev, don't link css files with ?inline query (#25822)
• nuxt: Pass external to navigate in custom <NuxtLink> (#25887)
• nuxt: Mark internal island components with @__PURE__ (#25842)
• nuxt: Use setTimeout before scrolling when navigating (#25817)
• nuxt: Add missing type for head in defineNuxtComponent (#25410)
• nuxt: Handle undefined paths in resolveTrailingSlashBehavior (ba6a4132b)
• nuxt: Set to.name to be undefined rather than deleting entirely (4ca1ab7cf)

📖 Documentation

• Enable more blocks for twoslash (#25830)
• Remove .ts extension when adding compiled files (#25855)
• Replace callout to new components (#25897)
• Fix incorrect wording (#25902)

🏡 Chore

• Use nuxt.config to enable pages for docs typecheck (72a2e23cc)
• Restore environment back to development (3f92cf04d)
• Unpin vite version 🙈 (d326e054d)
• nuxt: Use Exclude rather than Omit (3fc4231d3)

🤖 CI

• Typecheck code samples in docs (#25777)
• Update link to stackblitz mcve page (59dd5fd93)

❤️ Contributors

• Daniel Roe (@danielroe)
• Mateusz Kulpa (@mateuszkulpa)
• Jonathan Walters (@Chalks)
• Josh Layton (@jl8n)
• Julien Huang (@huang-julien)
• Damian Głowala (@DamianGlowala)
• Florent Delerue (@Flosciante)
• Alexander Lichter (@manniL)
• Anthony Fu (@antfu)
• OnlyWick (@OnlyWick)
• Michał Zarach (@michalzaq12)
• Miha Sedej (@tresko)

3.10.2 is a regularly-scheduled patch release.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the vue and unjs ecosystems.

👉 Changelog

compare changes

🩹 Fixes

• nuxt: Export refreshCookie (#25635)
• nuxt: Allow prefetching urls with query string (#25658)
• nuxt: Remove undefined keys in route object (#25667)
• vite: Treat .pcss extension as a CSS extension (#25673)
• nuxt: Don't check for layout/page with <ClientOnly> (#25714)
• vite: Strip query strings for style chunk filenames (#25764)
• nuxt: Inline entry styles before component styles (#25749)
• vite: Optimise layer dependencies with vite (#25752)
• nuxt: Don't add extra baseURL on server useRequestURL (#25765)
• schema: Use rootDir, not process.cwd, for modulesDir (#25766)
• nuxt: Only warn for useId if attrs were not rendered (#25770)
• kit: Don't mutate existing component entry when overriding (#25786)

📖 Documentation

• Fix typo in useAsyncData docs (#25644)
• Add quotes to clarify what site title is in example (#25669)
• Enable twoslash for some code snippets (#25679)
• Add prepend option docs for addComponentsDir (#25683)
• Extend auto-scanned layer directories (#25720)
• Improve wording in seo docs (#25692)
• Add how to debug nuxt with node inspector (#25731)
• <script setup> changed to <script setup lang="ts"> ([#25750](https://github.com//pull/25750))
• Add missing export defaults for nuxt config (#25774)
• Add import statement for mountSuspended (#25783)
• Pass event to useRuntimeConfig (#25788)

🏡 Chore

• schema: Add missing closing code block (#25641)

❤️ Contributors

• Sam Blowes (@blowsie)
• Daniel Roe (@danielroe)
• yoshihirokurosaki (@irishkooky)
• Eduardo San Martin Morote (@posva)
• Mahdi Shah Abbasian (@shahabbasian)
• João Carmona (@jpsc)
• Naim Ahmed Shuvo (@shuvo-me)
• Denis L (@DenisLug)
• GJSSSS (@gjssss)
• Anthony Fu (@antfu)
• Aman Desai (@amandesai01)
• Stephen Strange (@byStrange)
• Žan Fras (@frasza)
• Santiago Morales (@Aleroms)
• Hendrik Heil (@hendrikheil)

3.10.1 is a regularly-scheduled patch release.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the vue and unjs ecosystems.

👉 Changelog

compare changes

🔥 Performance

• nuxt: Clear route meta build cache when pages change (#25514)

🩹 Fixes

• nuxt: Fix syntax error when serializing route meta (#25515)
• nuxt: Only request animation frame on client (#25569)
• schema: Correctly set value for app.viewTransition (#25581)
• nuxt: Correct return type of refresh functions (#25568)
• nuxt: Broadcast cookie change in correct format (#25598)
• nuxt: Generate typed route declarations when building (#25593)
• nuxt: Remove key from useId type signature (#25614)
• nuxt: Remove $ from generated id in useId (#25615)
• nuxt: Don't set default rel for same-site external links (#25600)
• nuxt: Warn if inheritAttrs: false when using useId (#25616)
• nuxt: Fetch non-server rendered islands when hydrating (#25613)
• nuxt: Don't check page/layout usage when redirecting (#25628)

💅 Refactors

• nuxt: Improve NuxtLink types (#25599)

📖 Documentation

• Correct typo (#25523)
• Add and link to a section on Nuxt context (#23546)
• Explain how to set <NuxtLink> defaults in nuxt config (#25610)

🏡 Chore

• Use pathe in internal tests (e33cec958)
• nuxt: Rename nuxt -> nuxtApp internally for consistency (c5d5932f5)

🤖 CI

• Fix playwright cache (#25527)
• Retry flaky test when running in Windows with Webpack (#25536)
• Retry flaky test when running in Windows with Webpack (#25543)
• Retry flaky test when using Webpack (#25550)
• Simplify label PR workflow (#25579)

❤️ Contributors

• Daniel Roe (@danielroe)
• Julien Huang (@huang-julien)
• Harlan Wilton (@harlan-zw)
• Bobbie Goede (@BobbieGoede)
• xjccc (@xjccc)
• Ryan Clements (@RyanClementsHax)
• Enkot (@enkot)
• Damian Głowala (@DamianGlowala)
• Ted de Koning (@tdekoning)
• Troy Ciesco (@troyciesco)
• Michael Brevard (@GalacticHypernova)
• Arslan Ali (@warlock1996)

3.10.0 is the next minor/feature release.

👀 Highlights

v3.10 comes quite close on the heels of v3.9, but it's packed with features and fixes. Here are a few highlights.

✨ Experimental shared asyncData when prerendering

When prerendering routes, we can end up refetching the same data over and over again. In Nuxt 2 it was possible to create a 'payload' which could be fetched once and then accessed in every page (and this is of course possible to do manually in Nuxt 3 - see this article).

With #24894, we are now able to do this automatically for you when prerendering. Your useAsyncData and useFetch calls will be deduplicated and cached between renders of your site.

export defineNuxtConfig({ 
  experimental: { 
    sharedPrerenderData: true
  } 
}) 

👉 See full documentation.

🆔 SSR-safe accessible unique ID creation

We now ship a useId composable for generating SSR-safe unique IDs (#23368). This allows creating more accessible interfaces in your app. For example:

<script setup>
const emailId = useId()
const passwordId = useId()
</script>

<template>
  <form>
    <label :for="emailId">Email</label>
    <input
      :id="emailId"
      name="email"
      type="email"
    >
    <label :for="passwordId">Password</label>
    <input
      :id="passwordId"
      name="password"
      type="password"
    >
  </form>
</template>

✍️ Extending app/router.options

It's now possible for module authors to inject their own router.options files (#24922). The new pages:routerOptions hook allows module authors to do things like add custom scrollBehavior or add runtime augmenting of routes.

👉 See full documentation.

Client-side Node.js support

We now support (experimentally) polyfilling key Node.js built-ins (#25028), just as we already do via Nitro on the server when deploying to non-Node environments.

That means that, within your client-side code, you can import directly from Node built-ins (node: and node imports are supported). However, nothing is globally injected for you, to avoid increasing your bundle size unnecessarily. You can either import them where needed.

import { Buffer } from 'node:buffer'
import process from 'node:process'

Or provide your own polyfill, for example, inside a Nuxt plugin.

// ~/plugins/node.client.ts
import { Buffer } from 'node:buffer'
import process from 'node:process'

globalThis.Buffer = Buffer
globalThis.process = process

export default defineNuxtPlugin({})

This should make life easier for users who are working with libraries without proper browser support. However, because of the risk in increasing your bundle unnecessarily, we would strongly urge users to choose other alternatives if at all possible.

🍪 Better cookie reactivity

We now allow you to opt-in to using the CookieStore. If browser support is present, this will then be used instead of a BroadcastChannel to update useCookie values reactively when the cookies are updated (#25198).

This also comes paired with a new composable, refreshCookie which allows manually refreshing cookie values, such as after performing a request. See full documentation.

🏥 Detecting anti-patterns

In this release, we've also shipped a range of features to detect potential bugs and performance problems.

• We now will throw an error if setInterval is used on server (#25259).
• We warn (in development only) if data fetch composables are used wrongly (#25071), such as outside of a plugin or setup context.
• We warn (in development only) if you are not using <NuxtPage /> but have the vue-router integration enabled (#25490). (<RouterView /> should not be used on its own.)

🧂 Granular view transitions support

It's now possible to control view transitions support on a per-page basis, using definePageMeta (#25264).

You need to have experimental view transitions support enabled first:

export default defineNuxtConfig({
  experimental: {
    viewTransition: true
  },
  app: {
    // you can disable them globally if necessary (they are enabled by default)
    viewTransition: false
  }
})

And you can opt in/out granularly:

// ~/pages/index.vue
<script setup lang="ts">
definePageMeta({
  viewTransition: false
})
</script>

Finally, Nuxt will not apply View Transitions if the user's browser matches prefers-reduced-motion: reduce (#22292). You can set viewTransition: 'always'; it will then be up to you to respect the user's preference.

🏗️ Build-time route metadata

It's now possible to access routing metadata defined in definePageMeta at build-time, allowing modules and hooks to modify and change these values (#25210).

export default defineNuxtConfig({
  experimental: {
    scanPageMeta: true
  }
})

Please, experiment with this and let us know how it works for you. We hope to improve performance and enable this by default in a future release so modules like @nuxtjs/i18n and others can provide a deeper integration with routing options set in definePageMeta.

📦 Bundler module resolution

With #24837, we are now opting in to the TypeScript bundler resolution which should more closely resemble the actual way that we resolve subpath imports for modules in Nuxt projects.

'Bundler' module resolution is recommended by Vue and by Vite, but unfortunately there are still many packages that do not have the correct entries in their package.json.

As part of this, we opened 85 PRs across the ecosystem to test switching the default, and identified and fixed some issues.

If you need to switch off this behaviour, you can do so. However, please consider raising an issue (feel free to tag me in it) in the library or module's repo so it can be resolved at source.

export default defineNuxtConfig({
  future: {
    typescriptBundlerResolution: false
  }
})

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

-->

👉 Changelog

compare changes

🚀 Enhancements

• nuxt: tryUseNuxtApp composable (#25031)
• nuxt: Add experimental sharedPrerenderData option (#24894)
• schema: Default to bundler module resolution (#24837)
• nuxt: Warn if data fetch composables are used wrongly (#25071)
• nuxt: Add pages:routerOptions hook (#24922)
• Experimental client-side Node.js compatibility (#25028)
• nuxt: Throw error if setInterval is used on server (#25259)
• nuxt: refreshCookie + experimental CookieStore support (#25198)
• nuxt: Allow controlling view transitions in page meta (#25264)
• nuxt: Slow down loading indicator when approaching 100% (#25119)
• nuxt: Experimentally extract route metadata at build time (#25210)
• nuxt: useId composable (#23368)

🔥 Performance

• vite: Avoid endsWith when checking for whitespace (#24746)

🩹 Fixes

• nuxt: Disable View Transitions if prefers-reduced-motion (#22292)
• nuxt: Add declaration file with correct node16 imports (#25266)
• nuxt: Allow omitting fallback in island response (#25296)
• schema: Remove defineModel option as it is now stable (#25306)
• nuxt: Overwrite island payload instead of merging (#25299)
• vite: Pass hidden sourcemap values to vite (#25329)
• nuxt: ...

3.9.3 is a hotfix release to address a regression with CSS in development

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the vue and unjs ecosystems.

👉 Changelog

compare changes

🩹 Fixes

• nuxt: Render stylesheets in dev for non-islands (#25243)
• nuxt: Don't set 2x data-island-uid for island children (#25245)
• nuxt: Don't share object between raw cookie and cookie ref (#25255)

📖 Documentation

• Corrects variable name used in comment (#25238)
• Deleted an extra character (#25248)
• Remove space before colon (#25251)

✅ Tests

• Add separate suspense test suite (#22947)

❤️ Contributors

• Danila Rodichkin (@daniluk4000)
• Anthony Fu (@antfu)
• Julien Huang (@huang-julien)
• Mustafa60x (@mustafa60x)
• Александр Дьяконов (@Holiden)
• Flowern (@FlorianWerndl)
• Daniel Roe (@danielroe)

3.9.2 is a regularly scheduled patch release.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the vue and unjs ecosystems.

👉 Changelog

compare changes

🔥 Performance

• nuxt: Iterate rather than using Object.fromEntries (#24953)

🩹 Fixes

• nuxt: Add missing script blocks before island transform (#25148)
• kit: Improve types for options in addTemplate (#25109)
• nuxt: Apply more import protections for nitro runtime (#25162)
• nuxt: Sort pages/ files in en-US locale (#25195)
• nuxt: Check for layout after nextTick (#25197)
• nuxt: Set nitro log level to match nuxt options (#25213)
• nuxt: Await async payload revivers (#25222)
• nuxt: Render user-inserted links in island responses (#25219)

💅 Refactors

• nuxt: Refactor island response + improve rendering (#25190)
• nuxt: Rename to data-island-component (#25232)

📖 Documentation

• Correct nuxt image discussion link (#25090)
• Fix typo (#25100)
• Suggest using <NuxtPage> rather than <RouterView> (#25106)
• Fix typo (#25127)
• Add demo for view transitions api (3c5ea3457)
• Remove reference to @nuxt/bridge-edge (3f09ddc31)
• Remove bridge recommendation only relevant Vue <= 2.6.14 (7bb90f587)
• Bump nuxt 2 version (98fb2be07)
• Remove invalid nuxi aliases (#25209)
• Add --log-level description (#25211)
• Added immediate: false in the appropriate example (#25224)
• Mention .global.vue filename for global components (#25144)
• Clarify reactivity in composables directory (#23731)
• Remove lagon from deployment providers (#24955)
• Add eslint setup guide (#24976)
• Add information on custom path regexp in definePageMeta (#25073)
• Fix addDevServerHandler API (#25233)
• Mention installing nuxi for bridge (637f5622d)

🏡 Chore

• Use v3 branch sandbox in issue template (#25174)

❤️ Contributors

• Daniel Roe (@danielroe)
• Julien Huang (@huang-julien)
• Larry Williamson (@L422Y)
• Chris Visser (@chris-visser)
• Maxime Pauvert (@maximepvrt)
• Nils Wiesinger (@warflash)
• chris-basebone (@chris-basebone)
• Alexander Lichter (@manniL)
• Bertil Johannes Ipsen (@bipsen)
• Matej Černý (@CernyMatej)
• kongmoumou (@kongmoumou)
• Yi-Ru Lan (@awdr74100)
• Kiarttipum Charoenpojvajana (@44kia244)
• Pooya Parsa (@pi0)
• Inesh Bose (@ineshbose)
• Sébastien Chopin (@Atinux)
• Petar Nikolov (@petarvnikolov)
• Michael Brevard (@GalacticHypernova)
• toto6038 (@toto6038)
• gal-cernilogar (@gal-cernilogar)
• Shoshana Connack (@moshetanzer)

2.17.3 is the next patch release for the 2.x branch.

👉 Changelog

compare changes

💅 Refactors

• Migrate to hookable package (#24426)

🏡 Chore

• Fix invalid package files with npm pkg fix (4d0474c4b)

✅ Tests

• Skip lib check with vue-tsc test (90ffd8170)

🤖 CI

• Split type check into separate test (40f1f301e)

❤️ Contributors

• Andrey Yolkin (@AndreyYolkin)
• Daniel Roe (@danielroe)