Bump vue from 2.6.11 to 3.0.9

[dependabot-preview]

Bumps vue from 2.6.11 to 3.0.9.

Release notes

Sourced from vue's releases.

v3.0.9

Please refer to CHANGELOG.md for details.

v3.0.8

Please refer to CHANGELOG.md for details.

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.

... (truncated)

Changelog

Sourced from vue's changelog.

3.0.9 (2021-03-27)

Bug Fixes

• compiler-core: fix slot source location (#3494) (e752bdd)
• runtime-core: fix kebab-case prop required warning (2121c32), closes #3495 #3363
• runtime-core: remove dev-only props property from setup context for consistency (#3492) (4549e65)
• ensure backwards compat for pre-compiled sfc components (37c1709), closes #3493

3.0.8 (2021-03-26)

Bug Fixes

• compiler: properly bail stringfication for nested slot elements (f74b16c)
• compiler-core: allow unicode to appear in identifiers (#3443) (ebedccc), closes #3440
• compiler-core: avoid generating useless createVNode helper (#2938) (7715c49), closes #2739
• compiler-core: detect v-if branch root with comment as dev fragment (#2785) (4bf7ba1), closes #2780
• compiler-core: fix the detection of forwarded slots with v-if or v-for (#3353) (602b58e), closes #3347
• compiler-core: should not condense whitespace in RCDATA text mode (#3482) (b4b8215), closes #3479
• compiler-dom: stringifyStatic should remove attribute bindings with null value (#3477) (ca6aa01), closes #3475
• compiler-sfc: scope Id should not be attached to @keyframe breakpoint rules (#3308) (6cb9475), closes #3304
• compiler-sfc: should not rewrite scope variable (#3449) (bbc5fe6), closes #3445
• compiler-ssr: keep the order of imports expression for the fallback branch of SSR (#3448) (49f4072), closes #3447
• component: prioritize registered component over implicit self-reference via filename (abd129d), closes #2827
• hydration: handle camel-case tag name when performing match assertion (#3247) (9036f88), closes #3243
• KeepAlive: adapt keepalive for ssr (#3259) (e8e9b00), closes #3255
• reactivity: ensure computed can be wrapped by readonly (41e02f0), closes #3376
• reactivity: ensure that shallow and normal proxies are tracked seperately (close #2843) (#2851) (22cc4a7)
• reactivity: fix shallow readonly behavior for collections (#3003) (68de9f4), closes #3007
• rumtime-core: custom dom props should be cloned when cloning a hoisted DOM (#3080) (5dbe834), closes #3072
• runtime-core: cache props default values to avoid unnecessary watcher trigger (#3474) (44166b4), closes #3471
• runtime-core: ensure only skip unflushed job (#3406) (bf34e33)
• runtime-core: fix async component ref handling (#3191) (7562e72), closes #3188
• runtime-core: fix erraneous emits warnings w/ mixins (60d777d), closes #2651
• runtime-core: fix warning for absent props (#3363) (86ceef4), closes #3362
• runtime-core: handle error in async setup (#2881) (d668d48)
• runtime-core: handle error in async watchEffect (#3129) (eb1fae6)
• runtime-core: should call chained mixins and extends (#3040) (b58bb16), closes #3038
• runtime-core: should not cache property access during data() invocation (#3299) (6e88156), closes #3297
• runtime-core: should not track deps in pre flush watcher callbacks (d5824b9), closes #2728
• runtime-core: the select tag's multiple prop should be set before the children mounting (#3202) (2451dd8), closes #3199
• runtime-dom: support mounting app to svg container (#2929) (8ffcde2), closes #2926
• ssr: ensure async setup error handling work with suspense during ssr (2e71f07)
• ssr: fix memory leak when vnode component render throws error (da944cb), closes #3100
• ssr: properly update currentRenderingInstance state during ssr (8c3c14a), closes #2863
• ssr: respect render function from extends/mixins in ssr (#3006) (0a583d5), closes #3004

... (truncated)

Commits

• See full diff 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:

• 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]

Superseded by #53.