Bump @vue/runtime-core from 3.0.0-rc.10 to 3.0.7

[dependabot-preview[bot]]

Bumps @vue/runtime-core from 3.0.0-rc.10 to 3.0.7.

Release notes

Sourced from @vue/runtime-core's releases.

v3.0.7

Please refer to CHANGELOG.md for details.

v3.0.6

Please refer to CHANGELOG.md for details.

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.

... (truncated)

Changelog

Sourced from @vue/runtime-core's changelog.

3.0.7 (2021-03-01)

Bug Fixes

• compiler-sfc: handle more edge cases in default rewrite (1dedc19)
• deps: pin Rollup to 2.38 (34f354b), closes #3332
• runtime-core: properties in methods should be writable and enumerable in DEV (#3301) (e3568ba), closes #3300
• scheduler: ensure updates are always inserted in ascending id order (#3184) (45fae9d), closes #2768 #2829
• v-show: v-show takes higher priority than style attribute (#3230) (5ad4036), closes #2757
• init devtools after feature flag checks (d0ea745)

Performance Improvements

• reactivity: only call Set.add if doesn't already have value (#3307) (9cd9883)

3.0.6 (2021-02-24)

Bug Fixes

• compiler-core: do not mark v-for as stable on const bindings (734c65b), closes vitejs/vite#1956
• compiler-dom: ensure global build filename matches the one defined in package.json (close #3181) (#3185) (96b6433)
• compiler-dom: fix cdn entries (fcb6c89), closes #3181 #3185
• compiler-sfc: compiler blank srcset (#3005) (9dc816d)
• compiler-sfc: removeSpecifier issue when removing initial imports (script-setup) (#2729) (6d762a8)
• compiler-sfc: the empty lang attribute should be treated as no lang specified (#3051) (6d5b623)
• compiler-sfc: transformAssetUrls.base should not affect known module requests (2ea9867)
• compiler-sfc: treat const reactive() bindings as mutable (03360ce)
• compiler-ssr: avoid duplicated asset imports merged from component slot client branch (c69f4ea), closes vitejs/vite#2034
• devtools: init devtools in production (#2906) (4d9bcb7)
• devtools: send instance to devtools when it's mounted instead of created (4fecb27)
• docs: change reference to passed deadline (#2930) (de7f9d1)
• hmr: deep clone reused hoisted trees during dev (5a7a1b8), closes vitejs/vite#2022
• runtime-core: align $parent/$root with the template ref when using expose (#3158) (f43a3b0)
• runtime-core: allow overriding properties other than props (#3105) (73117f6)
• runtime-core: check the DEV_ROOT_FRAGMENT flag correctly in the dev environment (#2750) (347a879)
• runtime-core: component methods should override global properties in DEV (#3074) (2587f36)
• runtime-core: ensure app instance can be garbage collected after unmount (close #2907) (#2909) (60e05ef)
• runtime-core: instanceWatch should pass this.proxy to source as the first argument (#2753) (ec8fd10)
• runtime-dom: ensure readonly type prop on textarea is handled patched as attribute (#2888) (c5d147c), closes #2766
• kebab-case events are attached correctly on web components, see #2841 (#2847) (b302cbb)
• types: extract the correct props type for the DateConstructor (#2676) (48f0d29)
• ensure all published packages contan a LICENCE file (close #2650) (#2857) (6a48d23)
• remove superfluous spaces when normalizing class (#3083) (4b55142)
• runtime-dom: enable set form attr to null on form-elements (#2840) (#2849) (f262438)
• toRef: ref created from union typed prop can't be used in watch (#3048) (4ca4666)

... (truncated)

Commits

• 1a955e2 release: v3.0.7
• 45fae9d fix(scheduler): ensure updates are always inserted in ascending id order (#3184)
• 75964ab test: test case for #3300, #3301
• e3568ba fix(runtime-core): properties in methods should be writable and enumerable in...
• 4a96580 types: support object as props type (#3165)
• 3549662 dx(runtime-dom): warn config.isCustomElement usage in runtime-only build (#2945)
• d0ea745 fix: init devtools after feature flag checks
• d9f91e2 release: v3.0.6
• 5a7a1b8 fix(hmr): deep clone reused hoisted trees during dev
• ec8fd10 fix(runtime-core): instanceWatch should pass this.proxy to source as the fi...
• 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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)

[dependabot-preview[bot]]

Superseded by #126.