-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update dependency vue to v3 #1559
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/tongzhugroup/chemicaltools-web/8jwqUMJUnxBEoFBMaLjkCUvmJBzt [Deployment for 585140b failed] |
27a4127
to
21e1d7b
Compare
21e1d7b
to
140ce5b
Compare
140ce5b
to
ab135e7
Compare
ab135e7
to
d4b82f7
Compare
d4b82f7
to
a70bfb6
Compare
a70bfb6
to
6937b50
Compare
6937b50
to
a798ba6
Compare
a798ba6
to
38afdd5
Compare
38afdd5
to
473d7af
Compare
473d7af
to
585140b
Compare
8cb0aaa
to
a984e1e
Compare
2a58395
to
ce5dcc4
Compare
3e9c86c
to
fabaa09
Compare
de133f5
to
7b4f946
Compare
7b4f946
to
8bf529d
Compare
8bf529d
to
8d17dc0
Compare
b914ef0
to
ec3952a
Compare
ec3952a
to
fa5f6ad
Compare
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
This PR contains the following updates:
2.7.14
->3.3.4
Release Notes
vuejs/core (vue)
v3.3.4
Compare Source
Bug Fixes
v3.3.3
Compare Source
Bug Fixes
v3.3.2
Compare Source
Bug Fixes
v3.3.1
Compare Source
Bug Fixes
v3.3.0
Compare Source
For a detailed walkthrough of the new features in 3.3, please read the release blog post.
Features and deprecations listed here are aggregated from the beta and alpha releases. For full chronological history, bug fixes, and other minor features, please consult the individual logs of the 3.3 beta and alpha releases.
Features
defineSlots
macro andslots
option (#7982) (5a2f5d5)defineModel
macro anduseModel
helper (#8018) (14f3d74)<Suspense>
(#6736) (cb37d0b), closes #5513Deprecations
v3.2.47
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.46
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.45
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.44
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.43
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.42
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.41
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.40
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.39
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.38
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.37
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.36
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.35
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.34
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.33
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.32
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.31
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.30
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.29
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.28
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.27
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.26
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.25
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.24
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.23
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.22
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.21
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.20
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.19
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.18
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.17
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.16
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.15
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.14
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.13
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.12
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.11
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.10
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.9
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.8
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.7
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.6
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.5
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.4
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.3
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.2
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.1
Compare Source
Please refer to CHANGELOG.md for details.
v3.2.0
: Quintessential QuintupletsCompare Source
Please refer to the release blog post and CHANGELOG.md for details.
v3.1.5
Compare Source
Please refer to CHANGELOG.md for details.
v3.1.4
Compare Source
Please refer to CHANGELOG.md for details.
v3.1.3
Compare Source
Please refer to CHANGELOG.md for details.
v3.1.2
Compare Source
Please refer to CHANGELOG.md for details.
v3.1.1
Compare Source
Please refer to CHANGELOG.md for details.
v3.1.0
: PlutoCompare Source
Features
compilerOptions
when using runtime compiler (ce0bbe0)app.config.compilerOptions
(091e6d6)Performance Improvements
$attrs
update when it has actually changed (5566d39)Deprecations
app.config.isCustomElement
has been deprecated and should be now nested underapp.config.compilerOptions
. [Docs]delimiters
component option has been deprecated and should now be nested under thecompilerOptions
component option. [Docs]v-is
has been deprecated in favor ofis="vue:xxx"
[Docs]Minor Breaking Changes
this.$props
and theprops
object passed tosetup()
now always contain all the keys for declared props, even for props that are absent (4fe4de0). This has always been the behavior in Vue 2 and is therefore considered a fix (see reasoning in #3288). However, this could break Vue 3 code that relied on the keys for prop absence checks. The workaround is to use a Symbol default value for props that need absence checks:optionMergeStrategies
functions no longer receivethe component instance as the 3rd argument. The argument was technically
internal in Vue 2 and only used for generating warnings, and should not
be needed in userland code. This removal enables much more efficient
caching of option merging.
Bug Fixes
null
tovalue
(#3564) (e3f5dcb)props
argument (#3726) (9b160b9)RefSymbol
(#2548) (90aa835)v3.0.11
Compare Source
Please refer to CHANGELOG.md for details.
v3.0.10
Compare Source
Please refer to CHANGELOG.md for details.
v3.0.9
Compare Source
Please refer to CHANGELOG.md for details.
v3.0.8
Compare Source
Please refer to CHANGELOG.md for details.
v3.0.7
Compare Source
Please refer to CHANGELOG.md for details.
v3.0.6
Compare Source
Please refer to CHANGELOG.md for details.
v3.0.5
Compare Source
Please refer to CHANGELOG.md for details.
v3.0.4
Compare Source
Please refer to CHANGELOG.md for details.
v3.0.3
Compare Source
Please refer to CHANGELOG.md for details.
v3.0.2
Compare Source
Please refer to CHANGELOG.md for details.
v3.0.1
Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0
: One PieceToday 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:
@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):<script setup>
: syntactic sugar for using Composition API inside SFCs<style vars>
: state-driven CSS variables inside SFCsThese features are already implemented and available in Vue 3.0, but are provided only for the purpose of gathering feedback. They will remain experimental until the RFCs are merged.
We have also implemented a currently undocumented
<Suspense>
component, which allows waiting on nested async dependencies (async components or component withasync setup()
) on initial render or branch switch. We are testing and iterating on this feature with the Nuxt.js team (Nuxt 3 is on the way) and will likely solidify it in 3.1.Phased Release Process
The release of Vue 3.0 marks the general readiness of the framework. While some of the frameworks sub projects may still need further work to reach stable status (specifically router and Vuex integration in the devtools), we believe it's suitable to start new, green-field projects with Vue 3 today. We also encourage library authors to start upgrading your projects to support Vue 3.
Check out the Vue 3 Libraries Guide for details on all framework sub projects.
Migration and IE11 Support
We have pushed back the migration build (v3 build with v2 compatible behavior + migration warnings) and the IE11 build due to time constraints, and are aiming to focus on them in Q4 2020. Therefore, users planning to migrate an existing v2 app or require IE11 support should be aware of these limitations at this time.
Next Steps
For the near term after release, we will focus on:
For the time being, the documentation websites, GitHub branches, and npm dist tags for Vue 3 and v3-targeting projects will remain under
next
-denoted status. This meansnpm install vue
will still install Vue 2.x andnpm install vue@next
will install Vue 3. We are planning to switch all doc links, branches and dist tags to default to 3.0 by end of 2020.At the same time, we have started planning for 2.7, which will be the last planned minor release of the 2.x release line. 2.7 will be backporting compatible improvements from v3, and emit warnings on usage of APIs that are removed/changed in v3 to help with potential migration. We are planning to work on 2.7 in Q1 2021, which will directly become LTS upon release with an 18 months maintenance lifespan.
Trying It Out
To learn more about Vue 3.0, check out our new documentation website. If you are an existing Vue 2.x user, go directly to the Migration Guide.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.