Merged
Conversation
| datasource | package | from | to | | ---------- | ------- | ----- | ----- | | npm | nuxt | 3.4.3 | 3.5.0 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.4.3->3.5.0Release Notes
nuxt/nuxt
v3.5.0Compare Source
👀 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 (https://github.com/nuxt/nuxt/pull/20777), thanks to @antfu and @baiwusanyu-c.
defineOptionsmacroRead 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 (https://github.com/nuxt/nuxt/pull/19205, https://github.com/nuxt/nuxt/pull/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,shallowRefandshallowReactive.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:
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 (https://github.com/nuxt/nuxt/pull/20284).
You can follow the server component roadmap at https://github.com/nuxt/nuxt/issues/19772.
⏰ Environment config
You can now configure fully typed, per-environment overrides in your
nuxt.config:If you're authoring layers, you can also use the
$metakey to provide metadata that you or the consumers of your layer might use.Read more: https://github.com/nuxt/nuxt/pull/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 usingconst route = useRoute('route-name').🔎 'Bundler' module resolution
We now have full support within Nuxt for the
bundlerstrategy 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 thanNode16resolution.This turns on TypeScript's ability to 'follow' Node subpath exports. For example, if a library has a subpath export like
mylib/paththat is mapped tomylib/dist/path.mjsthen the types for this can be pulled in frommylib/dist/path.d.tsrather than requiring the library author to createmylib/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.jsonfor your~/serverdirectory (https://github.com/nuxt/nuxt/pull/20559). You can use by adding an additional~/server/tsconfig.jsonwith 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.extendhook 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:
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
prependoption toaddImportsDir(#20307)vite:configResolvedhook (#20411)webpack:configResolvedhook (#20412)addVitePluginandaddWebpackPlugin(#20525)nuxi analyzefrom cli (#20387)nuxtApp.runWithContext(#20608)typedPagesoption (#20367)runWithContextwithincallWithNuxt(#20775)useRequestURLhelper (#20765)<DevOnly>(#20817)addBuildPluginfor builder-agnostic implementation (#20587)NuxtClientFallback(#20336)🩹 Fixes
@nuxt/devtoolsmodule before core modules (#20595)<FragmentWrapper>(#20607)useErroris called with nuxt app context (#20585)nuxt_componentssr style andisVue(#20679)build.extendhook (#20605)fs.allowdirs to include app files (#20755).envchanges (#20501)<DevOnly>from parsed html (#20840)pages:extendto enable pages module (#20806)scrollBehavior(#20859)💅 Refactors
runtimeCompileroption out of experimental (#20606)resolvePath(#20756)📖 Documentation
useCookiedoes not share state (#20665)navigateToexamples (#20678)useSeoMetaanduseServerSeoMetapages (#20656)<NuxtLayout>when migratingerror.vue(#20690)awaitbefore lazy composable examples (7e7e006e9)pinia(#20778)🏡 Chore
markdownlint-cliupdate and prevent auto-update (675445f98)@ts-ignore(4f0d3d4ae).onlyin tests (ad97cb45a).mjsfiles (#20711)pnpm-workspace.yaml(#20751)externalVueremoval (a33d2e7ae)✅ Tests
🤖 CI
❤️ Contributors
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.