v3.2.0

[danielroe]

3.2.0 is the first minor release since we've started our new release schedule. We've brought it forward by a couple of weeks to include some goodies we want you to be able to play with soon.

👀 Highlights

• ⚡️ Nuxt DevTools

  You can opt-in to Nuxt DevTools per-project by going to the project root and running:

  npx nuxi@latest devtools enable

  Restart your Nuxt server and open your app in browser. Click the Nuxt icon on the bottom (or press Alt+D) to toggle the DevTools.

  More information in the docs!

• ✨ Better DX for overriding runtimeConfig, including inline type helpers
  
  

• 🪄 Automatically inferred return type for useFetch and $fetch based on method.

  It'll be a type error to use the wrong method when hitting an endpoint.

  Plus, if you have multiple methods served by a single endpoint (like ~/server/api/test.get.ts and ~/server/api/test.post.ts then the response type will match the kind of response you make.

• 🍪 useFetch is now integrated with event.$fetch, meaning cookies and context are now passed to api requests automagically within internal requests.

• 🔥 We now treeshake client-only components out of the server build more effectively using the experimental treeshakeClientOnly feature

  This is turned on by default but if you experience any issues, you can turn this off via:

  export default defineNuxtConfig({
    experimental: {
      treeshakeClientOnly: false
    }
  })

• 🛠️ New addRouteMiddleware kit utility for module authors

• 💪 Nitropack v2.2 has been released

  Lots of features, including runtime proxy support using route rules, nested fetch calls, binary and raw storage operations, exposed event.context.cf (cloudflare) and built-in session support.

  For full details see release notes

Changelog

compare changes
release

[madebyfabian]

Exciting stuff! Thanks to the team for their great work 💚

[DrJume]

Sadly, some PR references under the changelog section in the release (mostly ~#9000) are linking to wrong repo nuxt/nuxt when they should be linking to their correct PRs in nuxt/framework.

[DrJume]

Or the commit messages were not updated to link to the PRs which were copied from nuxt/framework to nuxt/nuxt?

[gkkirilov]

The link to Dev Tools docs doesn't work

[danielroe]

It's now public...

[oleghalin]

Having issue with useAsyncComponent after upgrade

And have next error:

[[vite-node] [plugin:vite:import-analysis] [VITE_ERROR] ./components/folder/component.vue:26:5 <br><pre>24 |      Object.defineProperty(__returned__, "__isScriptSetup", { enumerable: false, value: true });
25 |      return __returned__;
26 |    }
   |      ^
27 |  });
28 |  import { withCtx as _withCtx, toDisplayString as _toDisplayString, createTextVNode as _createTextVNode, resolveComponent as _resolveComponent, createVNode as _createVNode, mergeProps as _mergeProps } from "vue";</pre><br>
at ./components/folder/component.vue:26:5 ] {
  statusCode: 500,
  fatal: false,
  unhandled: false,
  statusMessage: 'Vite Error',
  __nuxt_error: true

If delete component mounts, but i get hydration issue for sure

[oleghalin]

While previous version works correctly

[danielroe]

You can try disabling experimental.treeShakeClientOnly - but would you open a new issue with a reproduction? 🙏

[oleghalin]

Yea, it works, i will create repro today

[oleghalin]

#18949

[michaelsynan]

Many thanks and respect to the Nuxt team!