codecov[bot]
commented
1 year ago Codecov Report
Merging #186 (be05772) into master (15a4fe9) will increase coverage by
12.82%. The diff coverage isn/a.
@@ Coverage Diff @@
## master #186 +/- ##
===========================================
+ Coverage 66.02% 78.84% +12.82%
===========================================
Files 6 6
Lines 156 156
===========================================
+ Hits 103 123 +20
+ Misses 53 33 -20 see 3 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.
github-actions[bot]
This PR contains the following updates:
3.3.3->3.4.1Release Notes
nuxt/nuxt
### [`v3.4.1`](https://togithub.com/nuxt/nuxt/releases/tag/v3.4.1) [Compare Source](https://togithub.com/nuxt/nuxt/compare/v3.4.0...v3.4.1) > 3.4.1 is a patch release. We've pulled it forward slightly to fix a couple of breaking bugs in 3.4.0. ##### 👉 Changelog [compare changes](https://togithub.com/nuxt/nuxt/compare/v3.4.0...v3.4.1) ##### 🩹 Fixes - **nuxt:** Set config on `ssrContext` in spa renderer ([#20216](https://togithub.com/nuxt/nuxt/pull/20216)) - **nuxt:** Mark entire payload as reactive ([#20218](https://togithub.com/nuxt/nuxt/pull/20218)) - **nuxt:** Add missing imports to `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 === '
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.