Bump @vue/reactivity from 3.0.0-rc.10 to 3.0.5

[dependabot]

Bumps @vue/reactivity from 3.0.0-rc.10 to 3.0.5.

Release notes

Sourced from @vue/reactivity's releases.

v3.0.5

Please refer to CHANGELOG.md for details.

v3.0.4

Please refer to CHANGELOG.md for details.

v3.0.3

Please refer to CHANGELOG.md for details.

v3.0.2

Please refer to CHANGELOG.md for details.

v3.0.1

Please refer to CHANGELOG.md for details.

v3.0.0 One Piece

Today we are proud to announce the official release of Vue.js 3.0 "One Piece". This new major version of the framework provides improved performance, smaller bundle sizes, better TypeScript integration, new APIs for tackling large scale use cases, and a solid foundation for long-term future iterations of the framework.

The 3.0 release represents over 2 years of development efforts, featuring 30+ RFCs, 2,600+ commits, 628 pull requests from 99 contributors, plus tremendous amount of development and documentation work outside of the core repo. We would like to express our deepest gratitude towards our team members for taking on this challenge, our contributors for the pull requests, our sponsors and backers for the financial support, and the wider community for participating in our design discussions and providing feedback for the pre-release versions. Vue is an independent project created for the community and sustained by the community, and Vue 3.0 wouldn't have been possible without your consistent support.

Taking the "Progressive Framework" Concept Further

Vue had a simple mission from its humble beginning: to be an approachable framework that anyone can quickly learn. As our user base grew, the framework also grew in scope to adapt to the increasing demands. Over time, it evolved into what we call a "Progressive Framework": a framework that can be learned and adopted incrementally, while providing continued support as the user tackles more and more demanding scenarios.

Today, with over 1.3 million users worldwide*, we are seeing Vue being used in a wildly diverse range of scenarios, from sprinkling interactivity on traditional server-rendered pages, to full-blown single page applications with hundreds of components. Vue 3 takes this flexibility even further.

Layered internal modules

Vue 3.0 core can still be used via a simple <script> tag, but its internals has been re-written from the ground up into a collection of decoupled modules. The new architecture provides better maintainability, and allows end users to shave off up to half of the runtime size via tree-shaking.

These modules also exposes lower-level APIs that unlocks many advanced use cases:

• The compiler supports custom AST transforms for build-time customizations (e.g. build-time i18n)
• The core runtime provides first-class API for creating custom renderers targeting different render targets (e.g. native mobile, WebGL or terminals). The default DOM renderer is built using the same API.
• The @vue/reactivity module exports functions that provide direct access to Vue's reactivity system, and can be used as a standalone package. It can be used to pair with other templating solutions (e.g. lit-html) or even in non-UI scenarios.

New APIs for tackling scale

The 2.x Object-based API is largely intact in Vue 3. However, 3.0 also introduces the Composition API - a new set of APIs aimed at addressing the pain points of Vue usage in large scale applications. The Composition API builds on top of the reactivity API and enables logic composition and reuse similar to React hooks, more flexible code organization patterns, and more reliable type inference than the 2.x Object-based API.

Composition API can also be used with Vue 2.x via the @vue/composition-api plugin, and there are already Composition API utility libraries that work for both Vue 2 and 3 (e.g. vueuse, vue-composable).

Performance Improvements

Vue 3 has demonstrated significant performance improvements over Vue 2 in terms of bundle size (up to 41% lighter with tree-shaking), initial render (up to 55% faster), updates (up to 133% faster), and memory usage (up to 54% less).

... (truncated)

Changelog

Sourced from @vue/reactivity's changelog.

3.0.5 (2020-12-30)

Note: this release contains a type-only change that requires TypeScript 4.0+, which may cause build issues in projects still using TS 3.x.

Bug Fixes

• compiler-core: fix missing createVNode import on nested v-for (ad4d391), closes #2718
• compiler-sfc: should keep template nodes with no content (#2468) (5b9b37f), closes #2463
• compiler-sfc: support transforming asset urls with full base url. (#2477) (db786b1)
• runtime-core: component mount anchor memory leak (#2459) (3867bb4), closes #2458
• runtime-core: skip patchBlockChildren if n1.dynamicChildren is null (#2717) (c59897c), closes #2715 #2485
• runtime-dom: support mounting app on ShadowRoot (#2447) (b2189ba), closes #2399
• ssr: properly handle ssr empty slot and fallback (88f6b33)
• transition: ensure manual style manipulation in transition leave hooks work (cbaa380), closes #2720
• transition: ensure styles from *-leave-active trigger transition (#2716) (3f8f9b6), closes #2712

Features

• devtools: send instance (3626ff0)

3.0.4 (2020-12-02)

Bug Fixes

• async-component: forward refs on async component wrapper (64d4681), closes #2671
• attr-fallthrough: ensure consistent attr fallthrough for root fragments with comments (3bc2914), closes #2549
• build: enable safari10 option for terser (#2472) (20a704f), closes #2470
• compiler-core: fix scope var reference check for v-on expressions (9db7095), closes #2564
• compiler-core: fix unintended imports in esm-bundler builds (55d99d7), closes #2258 #2515
• compiler-core: transform kebab case props to camelcase on slots (#2490) (ef59a30), closes #2488
• compiler-core/v-on: handle falsy values when caching v-on handlers (e4f09c1), closes #2605
• compiler-sfc: fix parsing error when lang="" is used on plain element (#2569) (5f2a853), closes #2566
• compiler-sfc: named imports from .vue file should not be treated as constant (085bbd5), closes #2699
• compiler-sfc: should not remove import statements with no specifier when compiling script setup (43eab92)
• compiler-ssr: generate correct children for transition-group (a5d6f80), closes #2510
• compiler-ssr: handle v-model checkbox with true-value binding (fe5428d)
• compiler-ssr: should not render key/ref bindings in ssr (5b62662)
• provide: support symbols in applyOptions (#2616) (7a1a782), closes #2615
• reactivity: ensure readonly on plain arrays doesn't track array methods. (#2506) (3470308), closes #2493
• reactivity: ensure add/set on reactive collections return the proxy (#2534) (6e46a57), closes #2530
• runtime-core: ensure keep-alive deep-watches include/explude props (#2551) (421205d), closes #2550
• runtime-core: ensure watchers are always registered to correct instance owner (#2495) (735af1c), closes #2381
• runtime-core: fix emit listener check on kebab-case events (#2542) (3532b2b), closes #2540
• runtime-core: handle static node move in production (bf16a57)
• runtime-core: remove static node in production mode (#2556) (2a9ba0c), closes #2553
• runtime-core: should pause tracking when initializing legacy options (#2524) (0ff2a4f), closes #2521

... (truncated)

Commits

• 5a5d037 release: v3.0.5
• d067fb2 release: v3.0.4
• e315d84 fix(types): fix ToRefs type on union value types
• 6e46a57 fix(reactivity): ensure add/set on reactive collections return the proxy (#2534)
• 3470308 fix(reactivity): ensure readonly on plain arrays doesn't track array methods...
• bd6e211 release: v3.0.3
• 8e20375 fix(types): ensure correct type for toRef and toRefs on existing refs
• 118502a chore: comments [ci skip]
• f2d03a5 release: v3.0.2
• 0e5a3c4 fix(reactivity): track length on for in iteration on Array
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[codecov-io]

Codecov Report

Merging #175 (a488d21) into master (e42c2e4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #175   +/-   ##
=======================================
  Coverage   80.75%   80.75%           
=======================================
  Files          97       97           
  Lines        2848     2848           
  Branches      422      452   +30     
=======================================
  Hits         2300     2300           
  Misses        547      547           
  Partials        1        1           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 55ac595...a488d21. Read the comment docs.

[dependabot]

Superseded by #266.