Skip to content

Bump @vue/reactivity from 3.0.0-rc.10 to 3.0.2#70

Closed
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/vue/reactivity-3.0.2
Closed

Bump @vue/reactivity from 3.0.0-rc.10 to 3.0.2#70
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/vue/reactivity-3.0.2

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Oct 21, 2020

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

Release notes

Sourced from @vue/reactivity's releases.

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).

In Vue 3, we have taken the approach of "compiler-informed Virtual DOM": the template compiler performs aggressive optimizations and generates render function code that hoists static content, leaves runtime hints for binding types, and most importantly, flattens the dynamic nodes inside a template to reduce the cost of runtime traversal. The user therefore gets the best of both worlds: compiler-optimized performance from templates, or direct control via manual render functions when the use case demands.

Improved TypeScript integration

Vue 3's codebase is written in TypeScript, with automatically generated, tested, and bundled type definitions so they are always up-to-date. Composition API works great with type inference. Vetur, our official VSCode extension, now supports template expression and props type checking leveraging Vue 3's improved internal typing. Oh, and Vue 3's typing fully supports TSX if that's your preference.

Experimental Features

We have proposed two new features for Singe-File Components (SFC, aka .vue files):

... (truncated)

Changelog

Sourced from @vue/reactivity's changelog.

3.0.2 (2020-10-20)

Bug Fixes

  • compiler: stringify values on v-text (#2432) (314ab2c), closes #2430
  • compiler-core: fix multiline member expression check (#2436) (6d2a1cb), closes #2426
  • reactivity: track length on for in iteration on Array (0e5a3c4), closes #2427
  • runtime-core: avoid mutating EMPTY_ARR when setting dev root (#2419) (edd49dc), closes #2413
  • runtime-core: avoid object prototype keys in property access cache (#2416) (ba881f9)
  • runtime-core: fix component .once listener logic (4bbb2b2)
  • runtime-core: non-stable Fragment should always unmount its children (#2445) (fff62e2), closes #2444
  • runtime-core: prevent self-injection (#2424) (111d04f), closes #2400
  • suspense: fix suspense nested child updates in template mode (0227b4a), closes #2214
  • types: h support for resolveComponent (#2402) (1f2a652), closes #2357
  • v-model: built in modifiers support on component (#2348) (128ec46), closes #2326

Features

  • compile-core: handle falsy dynamic args for v-on and v-bind (#2393) (052a621), closes #2388

3.0.1 (2020-10-15)

Bug Fixes

  • compiler-core: allow spaces between if-else branches (#2305) (89c5909), closes #2299
  • compiler-core: consistently remove comment nodes for pre tags in production (f411924), closes #2217
  • compiler-core: fix v-if key injection with v-on object syntax (#2368) (692197b), closes #2366
  • compiler-core: make v-once work with v-if/else-if/else (#2182) (9499871), closes #2035
  • compiler-ssr: fix SSR issue when dynamic and static class co-exist (#2354) (8539c0b)
  • hmr: full diff props for non-sfc component (#2359) (e78915a)
  • reactivity: should add allowRecurse to the effect (#2213) (ea1f87e), closes #2200
  • reactivity: should not trigger watch on computed ref when value is unchanged (390589e), closes #2231
  • reactivity: use resetTracking instead of enableTracking (#2174) (7cc09ca)
  • runtime-core: ensure this context for $nextTick callback (5c3e8e9), closes #2282
  • runtime-core: error handling for created/beforeCreate hooks (b392fe4), closes #2268
  • runtime-core: fix directive merging on component root (4d1ebb5), closes #2298
  • runtime-core: fix duplicated unmount traversal in optimized mode (376883d), closes #2169
  • runtime-core: fix provide function data access in extends/mixins (f06518a), closes #2300
  • runtime-core: fix SSR memoery leak due to props normalization cache (a66e53a), closes #2225
  • runtime-core: make errorCaptured return value handling consistent with Vue 2 (#2289) (4d20ac8), closes #2267
  • runtime-core: use consistent camelCase event casing for render functions (#2278) (62f2617), closes #2249
  • runtime-core: vnode.el is null in watcher after rerendering (#2295) (28d5fd7), closes #2170
  • runtime-core/template-refs: do not reset refs object before updates (25d53f0), closes #2283
  • runtime-dom: v-model should support number modifier with select tag (#2308) (d744b8a), closes #2252
  • sfc/style-vars: should attach css vars while subtree changed (#2178) (408a8ca), closes #2177

... (truncated)

Commits
  • f2d03a5 release: v3.0.2
  • 0e5a3c4 fix(reactivity): track length on for in iteration on Array
  • f17f0dd release: v3.0.1
  • 6b8cf99 chore: add missing space in warning message (#2266) [ci skip]
  • af1f5d3 refactor(reactivity): remove keyIsSymbol (#2262)
  • 7cc09ca fix(reactivity): use resetTracking instead of enableTracking (#2174)
  • 390589e fix(reactivity): should not trigger watch on computed ref when value is uncha...
  • ea1f87e fix(reactivity): should add allowRecurse to the effect (#2213)
  • d52d139 types: fix Typescript 4.1 compile error (#2219)
  • d8c1536 release: v3.0.0
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

@dependabot dependabot Bot added 📦 dependencies Pull requests that update a dependency file javascript labels Oct 21, 2020
@github-actions github-actions Bot added this to the v0.1.0 milestone Oct 21, 2020
@codecov-io
Copy link
Copy Markdown

Codecov Report

Merging #70 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #70   +/-   ##
=======================================
  Coverage   80.75%   80.75%           
=======================================
  Files          97       97           
  Lines        2848     2848           
  Branches      441      422   -19     
=======================================
  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 cb47820...c61228f. Read the comment docs.

@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Dec 3, 2020

Superseded by #133.

@dependabot dependabot Bot closed this Dec 3, 2020
@dependabot dependabot Bot deleted the dependabot/npm_and_yarn/vue/reactivity-3.0.2 branch December 3, 2020 05:19
@github-actions github-actions Bot removed this from the v0.1.0 milestone Dec 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

📦 dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants