v3.5.2

3.5.2 is a patch release focusing on bug fixes.

✅ 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: Use .test and hoist regexps where possible (#21011)

🩹 Fixes

• nuxt: Fix useLazyFetch types (#20989)
• nuxt: Scan component dirs case-sensitively (#20995)
• schema: Remove duplicate @default jsdoc tag (#21010)
• nuxt: Add type support for router composables without pages/ integration (397c54c9d)
• nuxt: Use simple incrementing id on client (#20992)
• nuxt: Treeshake <DevOnly> with webpack (#21013)
• nuxt: Await nuxt ready state before refreshNuxtData (#21008)
• nuxt: Show error page after fatal abortNavigation (#21047)
• nuxt: Normalize windows paths in granular watcher (#21066)
• nuxt: Omit Set-Cookie header if value is null (#21072)
• nuxt: Resolve modules relative to modulesDir (#21082)
• vite: Narrow vite-node inline pattern (#21224)

📖 Documentation

• Fix typo in modules directory example (#21014)
• Fix a typo in code example (#21057)
• Link to correct webpack css extraction loader (4e6369cef)
• api: Add render:island hook (#21065)
• Rewrite data fetching section (#21031)
• Improve data fetching docs (#21197)

🏡 Chore

• Move v2 docs to v2.nuxt.com (6d8c119a2)
• Add missing dependencies (9723add18)

✅ Tests

• Refactor type tests into a separate fixture (#21007)
• Close out some missing browser contexts (3bc3aeaf6)

❤️ Contributors

• Daniel Roe (@danielroe)
• Jongmin Yoon (@jongmin4943)
• Louis Haftmann (@LouisHaftmann)
• Clément Ollivier (@clemcode)
• Julien Huang (@huang-julien)
• Alexander (@xanderbarkhatov)
• Yue Yang (@g1eny0ung)
• Lucie (@lihbr)
• @Gecolay
• Lehoczky Zoltán (@Lehoczky)
• Sébastien Chopin (@Atinux)
• Haruaki OTAKE (@aaharu)

v3.5.1

3.5.1 is a patch release, with bug fixes and performance improvements.

✅ 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: Use granular watcher to avoid crawling ignored dirs (#20836)

🩹 Fixes

• webpack: Analyze report path (#20878)
• nuxt: Allow island renders without / route (#20894)
• nuxt: Infer useFetch method when generic is passed (#20797)
• nuxt: Prioritise vue app context when available (#20910)
• nuxt: Don't refresh when hydrating when data is present (#20916)
• nuxt: Resolve layer assets in relation to layer directory (#20932)
• nuxt: Don't match partial component names with prefix (#20939)
• kit: Resolve relative module paths when installing (#20896)
• nuxt: Exclude plugin declaration from non-existent files (#20974)
• nuxt: Use default type for initial value for composables (#20968)
• nuxt: Skip middleware for islands components (#20924)
• nuxt: Use resolvePath to handle edge cases for modules (#20975)

📖 Documentation

• Fix defaults in custom fetch example (#20898)
• Fix typo (#20907)
• Add pnpm test command to run whole test suite (4907660ff)
• Remove warning around experimental.renderJsonPayloads (891ba880e)
• Add example of 'alphabetical' plugin numbering (#20930)
• rendering: Improve rendering modes section (244c68108)
• rendering: Lint fix (ef8b5b593)
• Sync useAsyncData and useFetch types (#20935)
• Update static to isr (#20964)
• Add advanced usage example of useState (#20249)
• Add link to layers from pages/ docs (#20976)

🏡 Chore

• Rename script test for fixtures:payload (#20908)
• Pass ref to checkout (58ed8ec34)
• Remove outdated todo comment (b2a769a86)

🤖 CI

• Try different ref format (2b10dd7b7)

❤️ Contributors

• Paul Grau (@graup)
• Luciano Tonet (@lucianotonet)
• Daniel Roe (@danielroe)
• Julien Huang (@huang-julien)
• Haruaki OTAKE (@aaharu)
• Nate Emerson (@nateemerson)
• Jongmin Yoon (@jongmin4943)
• Sébastien Chopin (@Atinux)
• Aziz Ramdan Kurniawan (@azizramdan)
• @Gypsophyllite
• Wilson Pinto (@wilsonpinto)
• Lemon (@ww-lemon)
• Vasily Kuzin (@ExEr7um)
• Anthony Fu (@antfu)

v3.5.0

3.5.0 is a minor (feature) release with lots of new features to play with.

👀 Highlights

⚡️ Vue 3.3 released!

Vue 3.3 has been released, with lots of exciting features, particularly around type support. This also brings a significant improvement to data fetching when navigating between nested pages (#20777), thanks to @antfu and @baiwusanyu-c.

• new defineOptions macro
• 'generic' components
• typed slots and using external types in defineProps
• ... and more

Read the full release announcement for more details.

🙌 Nitropack v2.4

We've been working on lots of improvements to Nitro and these have landed already in Nitro v2.4 - you may already have this upgrade, which contains a lot of bug fixes, updates to the module worker format for Cloudflare, Vercel KV support and more.

One note: if you're deploying to Vercel or Netlify and want to benefit from incremental static regeneration, you should now update your route rules:

routeRules: {
--  '/blog/**': { swr: 3000 },
++  '/blog/**': { isr: 3000 },
}

Read the full release notes.

💖 New defaults

Rich JSON payload serialisation is now enabled by default (#19205, #20770). This is both faster and allows serialising complex objects in the payload passed from the Nuxt server to client (and also when extracting payload data for prerendered sites).

This now means that various rich JS types are supported out-of-the-box: regular expressions, dates, Map and Set and BigInt as well as NuxtError - and Vue-specific objects like ref, reactive, shallowRef and shallowReactive.

You can find an example in our test suite.

This is all possible due to Rich-Harris/devalue#58. For a long time, Nuxt has been using our own fork of devalue owing to issues serialising Errors and other non-POJO objects, but we now have transitioned back to the original.

You can even register your own custom types with a new object-syntax Nuxt plugin:

export default definePayloadPlugin(() => {
  definePayloadReducer('BlinkingText', data => data === '<original-blink>' && '_')
  definePayloadReviver('BlinkingText', () => '<revivified-blink>')
})

You can read more about how this works here.

🛝 Interactive server components

This feature should be considered highly experimental, but thanks to some great work from @huang-julien we now support interactive content within server components via slots (#20284).

You can follow the server component roadmap at #19772.

⏰ Environment config

You can now configure fully typed, per-environment overrides in your nuxt.config:

export default defineNuxtConfig({
  $production: {
    routeRules: {
      '/**': { isr: true }
    }
  },
  $development: {
    //
  }
})

If you're authoring layers, you can also use the $meta key to provide metadata that you or the consumers of your layer might use.

Read more: #20329.

💪 Fully typed pages

You can benefit from fully typed routing within your Nuxt app via this experimental integration with https://github.com/posva/unplugin-vue-router - thanks to some great work from @posva! Out of the box, this will enable typed usage of navigateTo, <NuxtLink>, router.push() and more. You can even get typed params within a page by using const route = useRoute('route-name').

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

🔎 'Bundler' module resolution

We now have full support within Nuxt for the bundler strategy of module resolution. We would recommend adopting this if possible. It has type support for subpath exports, for example, but more exactly matches the behaviour of build tools like Vite and Nuxt than Node16 resolution.

export default defineNuxtConfig({
  typescript: {
    tsConfig: {
      compilerOptions: {
        moduleResolution: 'bundler'
      }
    }
  }
})

This turns on TypeScript's ability to 'follow' Node subpath exports. For example, if a library has a subpath export like mylib/path that is mapped to mylib/dist/path.mjs then the types for this can be pulled in from mylib/dist/path.d.ts rather than requiring the library author to create mylib/path.d.ts.

⚗️ Separate server types

We plan to improve clarity within your IDE between the 'nitro' and 'vue' part of your app, and we've shipped the first part of this via a separate generated tsconfig.json for your ~/server directory (#20559). You can use by adding an additional ~/server/tsconfig.json with the following content:

{
  "extends": "../.nuxt/tsconfig.server.json"
}

Although right now these values won't be respected when type checking, you should get better type hints in your IDE.

💀 Deprecations

Although we have not typed or documented the build.extend hook from Nuxt 2, we have been calling it within the webpack builder. We are now explicitly deprecating this and will remove it in a future minor version.

✅ 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

• kit: Add prepend option to addImportsDir (#20307)
• nuxt: Add scoped helper for clearing error within boundary (#20508)
• nuxt: Auto import 'watchPostEffect' and 'watchSyncEffect' from vue (#20279)
• vite: Introduce vite:configResolved hook (#20411)
• webpack: Introduce webpack:configResolved hook (#20412)
• kit: Allow vite and webpack plugins to be prepended (#20403)
• nuxt: Add layer meta and env overrides to config types (#20329)
• test-utils: Add option to configure test server port (#20443)
• nuxt: Allow access to components within app (#20604)
• kit: Support passing getter to addVitePlugin and addWebpackPlugin (#20525)
• cli: Allow greater control of nuxi analyze from cli (#20387)
• nuxt: Add nuxtApp.runWithContext (#20608)
• deps: Upgrade to nitropack v2.4 (#20688)
• nuxt: Add experimental typedPages option (#20367)
• nuxt: Add apps to nuxt build-time instance (#20637)
• cli: Allow passing overrides to other nuxi commands (#20760)
• schema: Enable rich json payloads by default (#20770)
• deps: Update vue to v3.3 (#20478)
• nuxt: Use runWithContext within callWithNuxt (#20775)
• nuxt: Add useRequestURL helper (#20765)
• nuxt: Allow fallback production content in <DevOnly> (#20817)
• kit: addBuildPlugin for builder-agnostic implementation (#20587)
• nuxt: Allow keeping fallback for NuxtClientFallback (#20336)
• nuxt: Support separate server tsconfig (#20559)
• nuxt: Full scoped slots support for server components (#20284)
• nuxt: Support parallel plugins (#20460)

🩹 Fixes

• nuxt: Remove backwards-compatible runtimeConfig proxy (#20340)
• nuxt: Add @nuxt/devtools module before core modules (#20595)
• nuxt: Properly handle query for component wrapper (#20591)
• nuxt: Skip payload extraction for island context (#20590)
• nuxt: Remove internal <FragmentWrapper> (#20607)
• nuxt: Ensure useError is called with nuxt app context (#20585)
• nuxt: Run page meta plugin on all pages (and only pages) (#20628)
• nuxt, vite: Ignore nuxt_component ssr style and isVue (#20679)
• webpack: Warn when using deprecated build.extend hook (#20605)
• nuxt: Allow resolving client nuxt app to singl...

v3.4.3

3.4.3 is a patch release with the latest bug fixes. 🐞 It is expected that the next release will be v3.5, in approximately two weeks' time.

✅ 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: Don't call timeEnd unless we're debugging (#20424)
• nuxt: Use key to force server component re-rendering (#19911)
• nuxt: Add basic typings for <ClientOnly> (f1ded44e8)
• nuxt: Use event.node.req in cookie utility (#20474)
• deps: Relax upper node version constraint (#20472)
• nuxi,schema: Support devServer.https: true (#20498)
• nuxt: Throw 404 when accessing /__nuxt_error directly (#20497)
• nuxt: Use callAsync for executing hooks with context (#20510)
• nuxt: Improved typing support for app config (#20526)
• nuxt: Call app:error in SSR before rendering error page (#20511)
• nuxt: Restrict access to single renderer outside of test/rootDir (#20543)
• nuxt: Throw errors when running legacy asyncData (#20535)
• nuxt: Transform #components imports into direct component imports (#20547)
• nuxt: Return RenderResponse for redirects (#20496)

📖 Documentation

• Fix typos on docs homepage (#20456)
• Update links to vue-router docs (#20454)
• Remove RC reference and add link to vue migration build (#20485)
• Add cdn proxy section (#20408)
• Add a next steps link to first page of migration docs (#20512)
• Add custom fetch composable example (#20115)
• Adjust wrong link after repo migration (#20536)

✅ Tests

• Exclude default error pages from bundle test (ba320a558)
• Update snapshot (ac598e4f4)

🤖 CI

• Publish edge release with provenance (ec1503731)
• Run release script with node 18 (0d10e9734)
• Try releasing nuxt-edge with provenance (753c4c2a3)
• Run nuxt2 nightly release on node 14 again (48c034cf0)

❤️ Contributors

• Daniel Roe (@danielroe)
• Anthony Fu (@antfu)
• Julien Huang (@huang-julien)
• Andrew Luca (@iamandrewluca)
• Adrien Zaganelli (@adrienZ)
• Michael Gale (he/him) (@miclgael)
• Clément Ollivier (@clemcode)
• Paul Melero (@gangsthub)
• Jonas Thelemann (@dargmuesli)
• Johannes Przymusinski (@cngJo)
• Idorenyin Udoh (@idorenyinudoh)

v3.4.2

3.4.2 is a patch release with the latest bug fixes and performance improvements

✨ What's new?

Apart from the normal bug fixes, we have a couple things we should call out.

1. 🔥 We're now on Vite 4.3 (#20405). This was a performance-focused release and hopefully you'll be enjoying the speed improvements! Check out the release announcement for more info.
2. 👀 It's now possible to experimentally enable @parcel/watcher for the Nuxt dev watcher (#20179). This may improve performance if you're on Windows. You'll probably also want to install watchman in that case.

✅ 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: Share lazy component definitions (#20259)
• Remove unused deps and add implicit deps (#20356)
• Allow using @parcel/watcher for dev watcher (#20179)

🩹 Fixes

• vite: Set different cache dirs for client/server (#20276)
• nuxt: Generate hi-res sourcemaps (#20280)
• nuxt: Return type directly if not picking asyncData (#20288)
• nuxt: Provide more helpful error when instance unavailable (#20289)
• nuxt: Mark useRequestHeaders keys as optional (#20286)
• vite: Avoid serving arbitrary file in vite-node middleware (#20345)
• nuxt: Swap preloads for json/js payloads (#20375)
• nuxt: Handle pages with no content and log warning (#20373)
• test-utils: Import jest functions from @jest/globals (#20360)
• core,kit: Ensure module transpilation paths are dirs (#20396)
• schema: Rely on installed telemetry types (#19640)
• cli: Load kit from rootDir when preparing project (#20401)
• nuxt: Clone app config on server (#20278)

💅 Refactors

• nuxt: Rework and use isJS and isVue utilities consistently (#20344)
• vite: Use native isFileServingAllowed util (#20414)

📖 Documentation

• Update links on hooks page (#20296)
• Add brief information on debugging a nuxt app (#20282)
• Fix vue-tsc link (#20350)
• Update lint command for the documentation (#20399)

🏡 Chore

• Remove @ts-ignore and fix some issues (#20273)
• Maintain a 'next release' PR (e6cc4aa02)
• Set git user (2a596c2b3)
• Don't list dep updates in auto-changelog (8234bc18d)
• Update vite to v4.3 (#20405)

🤖 CI

• Don't run ci for release branches (f550976f7)
• Give write access to changelogensets (0518cdbff)

❤️ Contributors

• Daniel Roe (@danielroe)
• Harlan Wilton (@harlan-zw)
• Preet Mishra (@preetmishra)
• Lehoczky Zoltán (@Lehoczky)
• @BD103
• Anthony Fu (@antfu)

v3.4.1

3.4.1 is a patch release. We've pulled it forward slightly to fix a couple of breaking bugs in 3.4.0.

👉 Changelog

compare changes

🩹 Fixes

• nuxt: Set config on ssrContext in spa renderer (#20216)
• nuxt: Mark entire payload as reactive (#20218)
• nuxt: Add missing imports to <NuxtClientFallback> (#20237)
• nuxt: Improve handling of redirects within middleware (#20244)
• nuxt: Do not redirect when vue-router normalises url (#20247)

📖 Documentation

• Add a brief description of transform/pick (#20186)

✅ Tests

• Add js payload test suite (#20217)

❤️ Contributors

• Daniel Roe (@danielroe)
• David Kurek (@daviddomain)

v3.4.0

3.4.0 is a minor (feature) release for Nuxt 3 bringing exciting new features, including support for the View Transitions API, transferring rich JavaScript payloads from server to client - and much more.

👀 Highlights

🪄 View Transitions API Support

CleanShot.2023-04-11.at.18.00.47.mp4

You can see a demo on https://nuxt-view-transitions.surge.sh

You may have noticed that Chromium-based browsers now ship a new web platform API: the View Transitions API. This is an exciting new ability for native browser transitions which (among other things) have the ability to transition between unrelated elements on different pages.

Nuxt now ships with an experimental implementation, which will be under active development during the v3.4 release cycle. See the known issues in the linked PR.

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

✨ Payload Enhancements

We've merged a significant change to how Nuxt handles payloads (under an experimental flag). Payloads are used to send data from the server to the client when doing server-side rendering and avoid double data-fetching during the hydration phase.

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

With this new option enabled, this now means that various rich JS types are supported out-of-the-box: regular expressions, dates, Map and Set and BigInt as well as NuxtError - and Vue-specific objects like ref, reactive, shallowRef and shallowReactive.

You can find an example in our test suite.

This is all possible due to Rich-Harris/devalue#58. For a long time, Nuxt has been using our own fork of devalue owing to issues serialising Errors and other non-POJO objects, but we now have transitioned back to the original.

You can even register your own custom types with a new object-syntax Nuxt plugin:

export default definePayloadPlugin(() => {
  definePayloadReducer('BlinkingText', data => data === '<original-blink>' && '_')
  definePayloadReviver('BlinkingText', () => '<revivified-blink>')
})

You can read more about how this works here.

Note: this only affects payloads of the Nuxt app, that is, data stored within useState, returned from useAsyncData or manually injected via nuxtApp.payload. It does not affect data fetched from Nitro server routes via $fetch or useFetch although this is one area I am keen to explore further.

Preliminary testing shows a significant speed-up: 25% faster in total server response time for a very minimal app with a large JSON payload, but I'd urge you to run your own tests and share the results with us.

As mentioned, we're merging this behind a flag so we can test this broadly and gather feedback on the new approach. The most significant potential change is that the payload is now no longer available on window.__NUXT__ immediately. Instead, we now need to initialise the Nuxt app to parse the payload so any code that accesses __NUXT__ will need to be run in a plugin or later in the Nuxt app lifecycle. Please feel free to raise an issue if you foresee or encounter issues in your projects.

🎁 Object-syntax Nuxt plugins

We now support object-syntax Nuxt plugins for better control over plugin order and easier registration of hooks.

export default defineNuxtPlugin({
  name: 'my-plugin',
  enforce: 'pre', // or 'post'
  async setup (nuxtApp) {
    // this is the equivalent of a normal functional plugin
  },
  hooks: {
    // You can directly register Nuxt app hooks here
    'app:created'() {
      const nuxtApp = useNuxtApp()
      // 
    }
  }
})

In future we plan to enable build optimizations based on the metadata you pass in your Nuxt plugins.

🛠️ Easier Devtools Configuration

It's even easier to enable Nuxt DevTools in your project: just set devtools: true in your nuxt.config file to enable devtools.

export default defineNuxtConfig({
  devtools: true
})

If it's not already installed, Nuxt will prompt to install it locally. This means you no longer need to have Nuxt DevTools enabled globally.

Note: the DevTools is still experimental and under active development, so do be prepared for occasional unexpected behaviour, and please report issues directly to https://github.com/nuxt/devtools 🙏

📚 Layers Improvements

We now support transforming ~/~~/@/@@ aliases within layers, meaning you now no longer need to use relative paths when importing within layers.

This should mean it is much easier to use a 'normal' Nuxt project as a layer without needing to specially write it as one.

🧸 Better Context Transforms

We now transform certain keys of definePageMeta and defineNuxtComponent which means you should have fewer issues with a missing Nuxt instance. This includes support accessing the Nuxt instance after an await within asyncData and setup functions for those still using the Options API. And you no longer need to wrap middleware and validate with defineNuxtRouteMiddleware when using async functions.

♻️ Ecosystem Updates

As usual, this release will pull in upstream improvements, including the new Consola v3 and Nitropack v2.3.3 (a new minor is expected shortly).

🚨 'Breaking fixes'

We've also taken the opportunity to do some cleanup in this minor release.

1. Previously it was possible to pass the x-nuxt-no-ssr header (undocumented) to force SPA rendering. We've now disabled this behaviour by default but you can get it back by setting experimental.respectNoSSRHeader to true. Alternatively, you can set event.context.nuxt.noSSR on the server to force SPA rendering.
2. We've removed the (deprecated) #head alias and also disabled the polyfill for @vueuse/head behaviour by default. (It can still be enabled with experimental.polyfillVueUseHead.)
3. We've removed the (deprecated) experimental.viteNode option. It can be configured instead with vite.devBundler.
4. We've deprecated accessing public runtime config without the public key. This was an undocument compatibility measure with Nuxt 2 and we plan to remove it entirely in v3.5.
5. To fix a bug with our vue-router integration, we now generate a slightly different path matching syntax. If you were relying on the exact path generated, have a look at #19902 for more information.

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

With Nuxt v3.4.0, we now advise that you explicitly install the @types/node version that matches your Node version.

👉 Changelog

compare changes

🚀 Enhancements

• nuxt: Warn in dev when useRoute is used in middleware (#20050)
• nuxt: Support disabling watch with useFetch (#19823)
• nuxt: Support ~/~~/@/@@ aliases within layers (#19986)
• nuxt: Respect custom dir.pages in page placeholder (#20079)
• nuxt: Support vue runtime compiler (#4762)
• test-utils: Allow mounting single component for testing (#5723)
• nuxt: Experimental option for rich json payloads (#19205)
• nuxt: Prompt to install devtools when it's enabled (#20126)
• Upgrade to consola v3.x prerelease (#20141)
• nuxt: Add experimental View Transitions API support (#20092)
• nuxt: Support async transform of object properties (#20182)
• nuxt: Support object-syntax plugins (#20003)
• nuxt: Add experimentalNoScripts route rule (#19805)
• nuxt: Add chokidar watcher debug timing (#20176)

🔥 Performance

• head: Disable @vueuse/head polyfill by default (#20131)

🩹 Fixes

• nuxt: End route param tokens manually (#19902)
• nuxt: Disable x-nuxt-no-ssr header by default (#20024)
• kit: Support calling Nuxt 2 modules with module container (#20023)
• nuxt: Add types for globally injected $config object ([#20081](https://github.c...

v3.3.3

3.3.3 is your regularly scheduled bugfix/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

🩹 Fixes

• schema: Prefer src to rootDir aliases (#19937)
• nuxt: Don't override options signature with schema (#19934)
• vite: Allow extending vue config per-environment (#19968)
• nuxt: Store payloads in cache without trailing slash (#19992)
• webpack: Transpile rest of nuxt runtime directories (#19936)
• nuxt: Suppress handled errors (#20002)
• vite: Remove separate rollup dependency (#20013)
• nuxt: Sync setResponseStatus signature with h3 (#19987)
• schema: Add export condition for nuxt2 support (1fd491f1a)

💅 Refactors

• vite: Use rollup types re-exported from vite (#20011)

📖 Documentation

• Fix pages:extend example (72724076b)
• Remove unused function call (#20021)
• Add explanation for middleware execution order (#20029)
• Fix a couple of typos (b083493ec)

🏡 Chore

• Remove unneeded types packages (e60cb2698)
• Use pnpm workspace protocol internally (#19962)
• Bump version of mkdist to 1.2.0 (a96451d2d)
• Fix fixture package.json files (8c2ca23c5)
• Fix typo in code comment (2f8e991b9)

✅ Tests

• Skip bundle size test in ecosystem-ci suites (434e2013e)
• Bump bundle size test by 100 bytes (5785908ec)

🤖 CI

• Run docs linting step on node 18 (1ae5b2c58)

❤️ Contributors

• Daniel Roe (@danielroe)
• Ben Hong (@bencodezen)
• Julien Le Coupanec (@LeCoupa)
• David Mignot (@idflood)

v3.3.2

3.3.2 is a patch release with plenty of bug fixes.

✅ 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: Experimentally disable vue server renderer nitro endpoint (#19825)

🩹 Fixes

• kit: Provide name to performance.mark() (#19687)
• nuxt: Unpause DOM updates on suspense resolve (#19740)
• kit: Handle node 14 performance behaviour (#19733)
• webpack: Transpile app directory (#19773)
• nuxt: Unset context after app is created (#19753)
• cli: Watch dist and register restart hook after nuxt is ready (#19736)
• nuxt: Ignore falsy modules (#19684)
• nuxt: Use h3 utilities to set response status/code (#19713)
• nuxt: Add temporary augmentation for webstorm (and docs) (#19400)
• nuxt: Handle external navigation to api routes (#19829)
• nuxt: Observe slot element in custom nuxt-link (#19802)
• nuxt: Directly render server components (#19605)
• vite: Support multiple rollup entries (#19842)
• nuxt: Ignore schema types that eval to any (#19835)
• nuxt: Use prerender cache for islands (#19822)
• nuxt: Add missing import in islands template (#19870)
• kit: Check if nuxt is restarting before updating templates (#19830)
• test-utils: Allow overriding nitro options (#19872)
• kit: Add legacy entrypoints for pre v3.3 usage (#19874)

📖 Documentation

• Fix auto-imports example (#19520, #19690)
• Update seo and meta page (#19697)
• introduction: First batch of improvements (98b9afa6d)
• Update module author guide (#18551)
• Add 'going further' section for custom routing (#19565)
• Improve installation prerequisites (c570ae272)
• Update custom routing link (8d644903b)
• Add backticks (#19721)
• Add link to layout transitions (#19770)
• Fix typo (#19775)
• Fix typo (#19779)
• Fix typo (#19785)
• Add missing comma (#19791)
• Update legacy server examples (#19797)
• Third-party state management and migration guide (#19798)
• Link to module request issue template (#19754)
• Improve swr documentation (#18743)
• Add another example for useAsyncData (#19225)
• Avoid $fetch in top-level <script setup> (#19357)
• Removing deprecated coming soon banner (#19817)
• Add serialization section to data fetching (#19336)
• Add protocol to superjson link (cebfcb3da)
• Update play on X links (8c11498a5)
• Add missing return statement (fc7867fb0)
• Replace @nuxt/kit example with node built-ins (#19873)
• Add layers video by LearnVue (d3d09d5d3)
• Improve components page (340725bb0)

🏡 Chore

• Add internal types for nitro/app (#19745)
• Remove unused TS directive (0b5ba6c3e)
• Bump package versions (6d7161270)
• Bump package versions (2580cc830)
• Bump package versions (3ee97b125)

✅ Tests

• Remove sourcemaps from minimal test (#19730)
• Bump bundle size (e57c797f2)
• Alias test-utils back to src again (8b06b06a0)

🤖 CI

• Test built packages (#19767)

❤️ Contributors

• Daniel Roe daniel@roe.dev
• Sébastien Chopin (@Atinux)
• Warflash nwiesinger67@gmail.com
• Pooya Parsa pyapar@gmail.com
• Harlan Wilton (@harlan-zw)
• Julien Huang julien.huang@outlook.fr
• Mehdi HosseinZade (@xtoolkit)
• Mahdi Boomeri mahdi@boomeri.dev
• Saeid Zareie
• Özüm Eldoğan (@ozum)
• Jakub Zomerfeld (@devzom)
• Alan Poulain contact@alanpoulain.eu
• Emil Rosenius
• Ege İliklier (@Maiquu)
• Anthony Fu anthonyfu117@hotmail.com
• Adrien Zaganelli (@adrienZ)
• Fahmi Elfituri (@fahmifitu)
• Kuizuo (@kuizuo)
• Cunzaizhuyi (@cunzaizhuyi)
• Cue hello@cuebit.dev
• Fleet Labs Ghana (@joeokat)
• Zack Hatlen (@zackha)
• Leopold Kristjansson (@leopoldkristjansson)
• Nick Medrano
• Matthew Woods mattwoods9170@gmail.com

v2.16.3

2.16.3 is a patch release with bug fixes.

👉 Changelog

compare changes

🩹 Fixes

• types: Add return type for error() (#19044)
• types: Bring types from less into namespace (#19738)
• types: Sync vue type augmentations with Vue 2.7 (#19526)
• config: Move preset to inner postcssOptions (#19518)
• webpack: Add node-fetch-native to externals list (#19755)

🏡 Chore

• Release all packages with latest tag except nuxt (4e9dcddcb)
• examples: Use 2.x version of nuxt instead of latest (#19737)
• Lint package files (6ca842e36)

❤️ Contributors

• Daniel Roe - @danielroe
• Olga Bulat - @obulat
• Rafał Chłodnicki - @rchl