v3.3.1 #19672
Pinned
danielroe
announced in
Announcements
v3.3.1
#19672
Replies: 3 comments 2 replies
-
amazing strides, congrats on the release! |
Beta Was this translation helpful? Give feedback.
0 replies
-
Well done everyone! |
Beta Was this translation helpful? Give feedback.
0 replies
-
Can you tell me the name of the font you are using? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
👀 Highlights
✨ Local module development DX
We've landed a raft of changes to enable local modules and improve DX. We now auto-scan your
~/modules
folder and register top level files there as modules in your project (#19394). When these files are changed, we'll automatically restart the nuxt server.export default defineNuxtConfig({ modules: [ '@nuxtjs/tailwindcss', - '~/modules/purge-comments' ] })
We also now expose
nuxt/kit
for easy access to kit composables in your local project without having to install@nuxt/kit
(#19422).♻️ Restarting Nuxt
You can add files to the
watch
array to automatically restart the server (#19530). This is likely to be particularly useful for module authors. You can also trigger a restart of the Nuxt server with the newrestart
hook (#19084). We also landed a couple of fixes on restarting the Nuxt server which should improve your experience when developing.🔥 Performance improvements
We've increased static asset maxAge to 1yr as a matter of best practice (#19335), and support tree-shaking more of your build (#19508). We also now support preloading
<NuxtLink>
s with a route in object-syntax (#19120).We also track how long it takes each module you use to perform its setup, and warn if it takes too long. You can see all these values by running your dev server with
DEBUG=1
You can also opt-in to some of Nuxt's internal optimisations by configuring composables to be treeshaken in a particular environment (#19383), or to have magic keys automatically injected (#19490) - primarily useful for module authors.
🐛 Error handling
We now handle chunk errors by default (#19086), meaning if your site updates with a redeploy, we automatically handle reloading it on navigation. You can disable this and handle it yourself with the new
reloadNuxtApp
composable. You can also setexperimental.restoreState
to preserve some of your app state across reloads.We also have a new experimental error handling component:
<NuxtClientFallback>
(nuxt/framework#8216) which can capture errors rendering on server, replace them with fallback content, and granularly trigger rerendering the part with an error on the client. This can be enabled withexperimental.clientFallback
- feedback very welcome!⚡️ Head improvements
We've migrated to use
unhead
directly (#19519) - and automatically tree-shake server-only head composables likeuseServerHead
from your client build (#19576), meaning you can have great SEO without needing to include meta tag logic that's relevant only for crawlers in your client build.There's also a new
useHeadSafe
composable that handles santising untrusted user input (#19548).🪵 Better logging in browser DevTools
Working with the Chrome DevTools team, we've landed a couple of features across the unjs + Nuxt ecosystem meaning we now have first-class support for hiding Nuxt internal stack traces from logs in your (Chromium-based, for now) browser (#19243). We also landed a couple of improvements with stacktraces involving Nuxt hooks (unjs/hookable#69 and unjs/hookable#68) implementing
console.createTask
.💪 Type improvements
Types for server API routes are now more correct - with non-serialisable types stripped out of the return type (unjs/nitro#1002).
We also now type more of
NuxtApp
and correctly type unknown injections for greater type-safety (#19643).And if you were struggling with correct types when using
transform
+default
with Nuxt data fetching composables, fear no more - we now infer the types correctly (#19487).⚗️ Nitro enhancements
This release comes with Nitro v2.3, which brings lots of improvements of its own. Check out the release for more info.
We now support
useAppConfig
in nitro server routes (#19489) - a long-awaited change. NowuseAppConfig
is consistently available throughout your app for non-runtime configuration from layers, modules, etc.We've also added a
nitro:build:public-assets
hook to allow modifying assets output from nitro's prerender/build phase (https://github.com/nuxt/nuxt/pull/196380.🛠️ Build changes
As part of moving towards first-class support for PNP and pnpm support without
--shamefully-hoist
, we've dropped support for some internal (deprecated) utilities using CJS resolve patterns (#19537, #19608). We also now resolve dependencies likenuxt
,@nuxt/kit
and more using ESM search-paths. We'll be keeping a close eye on this.We're also preparing the groundwork for support of new TypeScript Node16 module resolution (#19606), and as part of this have changed the format of our runtime output (using
.js
instead of.mjs
extensions, providingtypes
fields for subpath exports, and more).🗺️ Custom config schema (advanced)
We've been testing out an experimental feature to allow modules and users to extend the Nuxt config schema (#15592), and we've now enabled this by default (#19172). We expect this will be particularly useful for module and layer/theme authors, and should result in some nicer DX for their users.
Changelog
compare changes
This discussion was created from the release v3.3.0.
Beta Was this translation helpful? Give feedback.
All reactions