NuxtJS
v3.8.2

#nuxt3.8.2 is a patch release focusing on bug fixes

👉 Changelog

compare changes

🩹 Fixes

● vite: Skip warming up node builtins (#24162)
● vite: Provide default values for transformAssetUrls (#24173)
● nuxt: Wrap caught asyncData error in createError (#24093)
● nuxt: Include plugin templates in plugins.d.ts if they will be written (#23943)
● nuxt: Handle multi-line slots in islands (#24212)
● nuxt: Fix replace regex used for slots in islands SSR (#24255)
● vite: Use rollup replace plugin for typeof optimisations (#23903)
● nuxt: Provide route component names to KeepAlive cache (#24024)
● schema: Use scule types for runtimeConfig type hints (#23696)
● nuxt: Deeply unwrap headers/query for useFetch key (#24307)
● nuxt: Split component name case in each segment (#24318)
● nuxt: Do not compute useFetch key from headers (#23462, #24333)
● nuxt: Set framework info for nitro (#24340)
● schema: Add type for ignoreOptions (#24337)
● nuxt: Log errors rendering islands (#24356)

NuxtJS
v3.9.0

#nuxt3.9.0 is the next minor release.

👀 Highlights

A very merry Christmas to you and yours from all Nuxters involved in this release! 🎁🎄

We have lots of features packed into v3.9.0 and can't wait for you to try them out.

⚡️ Vite 5

This release comes with Vite 5 and Rollup 4 support. Module authors may need to check to ensure that any vite plugins you're creating are compatible with these latest releases.

This comes with a whole host of great improvements and bug fixes - check out the Vite changelog for more info.

✨ Vue 3.4 ready

This release is tested with the latest Vue 3.4 release candidate, and has the necessary configuration to take advantage of new features in Vue 3.4, including debugging hydration errors in production (just set debug: true) in your Nuxt config.

👉 To take advantage, just update your vue version once v3.4 is released, or try out the release candidate today:

{
  "dependencies": {
    "nuxt": "3.9.0",
    "vue": "3.4.0-rc.1",
    "vue-router": "latest"
  }
}

NuxtJS
v3.9.1

#nuxt3.9.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: Avoid multiple iterations in useRequestHeaders (#24853)
● kit,schema,nuxt: Refactor startsWith to array access (#24744)
● nuxt: Use single iteration when normalising routes (#24946)
● nuxt: Remove some line breaks when rendering html (#24888)

🩹 Fixes

● nuxt: Catch error in NuxtErrorBoundary with ssr: false (#24896)
● kit: Show correct error when module can't be loaded (#24957)
● nuxt: Deeply watch island props (#24986)
● nuxt: Don't show transition on initial page load (#24935)
● nuxt: Clone cookie to detect changes within object (#25007)
● nuxt: Do not warn about missing layouts on error page (#25008)

NuxtJS
v3.9.2

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

NuxtJS
v3.10.0

#nuxt3.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
  }
}) 

Important

NuxtJS
v3.10.1

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