Closed renovate[bot] closed 5 months ago
:tada: This PR is included in version 3.0.0-next.46 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
:tada: This PR is included in version 3.0.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
This PR contains the following updates:
3.9.3
->3.10.0
20.11.9
->20.11.10
9.0.6
->9.0.7
3.9.3
->3.10.0
Release Notes
nuxt/nuxt (@nuxt/webpack-builder)
### [`v3.10.0`](https://togithub.com/nuxt/nuxt/releases/tag/v3.10.0) [Compare Source](https://togithub.com/nuxt/nuxt/compare/v3.9.3...v3.10.0) > 3.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](https://roe.dev/blog/shared-data-nuxt-generate)). With [#24894](https://togithub.com/nuxt/nuxt/pull/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. ```ts [nuxt.config.ts] export defineNuxtConfig({ experimental: { sharedPrerenderData: true } }) ``` > \[!IMPORTANT]\ > It is particularly important to make sure that any unique key of your data is always resolvable to the same data. For example, if you are using `useAsyncData` to fetch data related to a particular page, you should provide a key that uniquely matches that data. (`useFetch` should do this automatically.) 👉 See [full documentation](https://nuxt.com/docs/guide/going-further/experimental-features#sharedprerenderdata). ##### 🆔 SSR-safe accessible unique ID creation We now ship a `useId` composable for generating SSR-safe unique IDs ([#23368](https://togithub.com/nuxt/nuxt/pull/23368)). This allows creating more accessible interfaces in your app. For example: ```vue [components/MyForm.vue] ``` ##### ✍️ Extending `app/router.options` It's now possible for module authors to inject their own `router.options` files ([#24922](https://togithub.com/nuxt/nuxt/pull/24922)). The new `pages:routerOptions` hook allows module authors to do things like add custom `scrollBehavior` or add runtime augmenting of routes. 👉 See [full documentation](https://nuxt.com/docs/guide/going-further/custom-routing#router-options). #####typicode/husky (husky)
### [`v9.0.7`](https://togithub.com/typicode/husky/releases/tag/v9.0.7) [Compare Source](https://togithub.com/typicode/husky/compare/v9.0.6...v9.0.7) - fix: typo and source `~/.huskyrc` correctly (compatibility with v8) - docs: fix example by [@typicode](https://togithub.com/typicode) in [https://github.com/typicode/husky/pull/1363](https://togithub.com/typicode/husky/pull/1363)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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.