Closed renovate[bot] closed 1 year ago
This PR contains the following updates:
^3.0.0
^3.4.3
^0.2.1
^0.3.1
^3.2.2
^8.29.0
^8.40.0
^0.28.5
^0.31.0
This PR contains the following updates:
^3.0.0->^3.4.3^0.2.1->^0.3.1^3.0.0->^3.4.3^3.2.2->^3.4.3^8.29.0->^8.40.0^3.2.2->^3.4.3^0.28.5->^0.31.0Release Notes
nuxt/nuxt
### [`v3.4.3`](https://togithub.com/nuxt/nuxt/releases/tag/v3.4.3) [Compare Source](https://togithub.com/nuxt/nuxt/compare/v3.4.2...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: ```sh 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](https://togithub.com/nuxt/nuxt/compare/v3.4.2...v3.4.3) ##### π©Ή Fixes - **nuxt:** Don't call `timeEnd` unless we're debugging ([#20424](https://togithub.com/nuxt/nuxt/pull/20424)) - **nuxt:** Use key to force server component re-rendering ([#19911](https://togithub.com/nuxt/nuxt/pull/19911)) - **nuxt:** Add basic typings for `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**](https://developer.chrome.com/docs/web-platform/view-transitions/). 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](https://togithub.com/nuxt/nuxt/pull/20092). ```ts export default defineNuxtConfig({ experimental: { viewTransition: true } }) ``` ##### β¨ Payload Enhancements We've merged a **[significant change to how Nuxt handles payloads](https://togithub.com/nuxt/nuxt/pull/19205)** (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. ```ts [nuxt.config.ts] 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](https://togithub.com/nuxt/nuxt/blob/main/test/fixtures/basic/pages/json-payload.vue) in our test suite. This is all possible due to [Rich-Harris/devalue#58](https://togithub.com/Rich-Harris/devalue/pull/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: ```ts [plugins/custom-payload-type.ts] export default definePayloadPlugin(() => { definePayloadReducer('BlinkingText', data => data === '