chore(deps): update all non-major dependencies with stable versions (patch) #167
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
requested review from
a team,
ValeryG,
kongponents-bot and
vaibhavrajsingh2001
as code owners
✅ Deploy Preview for kong-spec-editor ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
renovate
bot
force-pushed
the
renovate/patch-all-stable
branch
2 times, most recently
from
221d6eb to
2f331b7
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/patch-all-stable
branch
from
2f331b7 to
a1582ae
Compare
renovate
bot
changed the title
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
bot
force-pushed
the
renovate/patch-all-stable
branch
from
a1582ae to
4ed18e1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
>=3.2.4->>=3.2.7^10.6.1->^10.6.2>=4.0.4->>=4.0.5](https://renovatebot.com/diffs/npm/form-data@>=4.0.0 <4.0.4/4.0.4/4.0.5)^3.1.5->^3.1.6>=3.0.0-alpha.0->>=3.0.11](https://renovatebot.com/diffs/npm/vue@>=2.0.0-alpha.1 <3.0.0-alpha.0/3.0.0-alpha.0/3.0.11)Release Notes
cure53/DOMPurify (dompurify@<3.2.4)
v3.2.7: DOMPurify 3.2.7Compare Source
tagNameparameter to custom elementattributeNameCheck, thanks @nelstromhrefattributes, thanks @llamakkov3.2.6: DOMPurify 3.2.6Compare Source
matrix:as an allowed URI scheme, thanks @kleinesfilmroellchenv3.2.5: DOMPurify 3.2.5Compare Source
ALLOWED_URI_REGEXPusing the 'g' flag, thanks @hhk-pngvuejs/eslint-plugin-vue (eslint-plugin-vue)
v10.6.2Compare Source
Patch Changes
vue/no-duplicate-class-namesand correctly detect duplicates in combining expressions (#2980)TSImportTypeinvue/script-indentrule (#2969)vue/prefer-use-template-ref(#2982)form-data/form-data (form-data@>=4.0.0 <4.0.4)
v4.0.5Compare Source
Commits
16e0076@ljharb/eslint-config,eslint582246776d0deevuejs/language-tools (vue-tsc)
v3.1.6Compare Source
Features
<script setup>(#5805)Bug Fixes
createParsedCommandLineByJsonparsed incorrect options since v3.1.5 (#5768 (comment))vue.server.pathcompatible with Windows (#5772)getVIfNodeto supportv-else-ifdirectives (#5765) - Thanks to @serkodev!{}instead of its string value forstyle="..."(#5781) - Thanks to @KazariEX!v-bind="$attrs"loses navigation wheninferTemplateDollarAttrsis disabled (#5783)const props =completion in StringLiteral (#5786)$eltype for generic components usinginferComponentDollarEl(#5794)<script>content generates before<script setup>(#5795)bypassDefineComponenthack for better JS support (#4876) (#5379)Prettify<T>caused generic props gets inferred asunknown(#5667) - Thanks to @so1ve!<as operator in SFC scripts (#5801) - Thanks to @serkodev!isTypeScriptDocumentin VSCode fortypescript.preferences.autoImportSpecifierExcludeRegexesconfig support (#5364)vaporattr (#5496)Performance
:class- Thanks to @KazariEX!Other Changes
debuggerfrom virtual code for tsslint compatibilityref="xxx"rawTypeand__internal__.tsLs(#5808)createResolveModuleName(volarjs/volar.js#293) (#5644) - Thanks to @serkodev!vuejs/core (vue@>=2.0.0-alpha.1 <3.0.0-alpha.0)
v3.0.11Compare Source
Please refer to CHANGELOG.md for details.
v3.0.10Compare Source
Please refer to CHANGELOG.md for details.
v3.0.9Compare Source
Please refer to CHANGELOG.md for details.
v3.0.8Compare Source
Please refer to CHANGELOG.md for details.
v3.0.7Compare Source
Please refer to CHANGELOG.md for details.
v3.0.6Compare Source
Please refer to CHANGELOG.md for details.
v3.0.5Compare Source
Please refer to CHANGELOG.md for details.
v3.0.4Compare Source
Please refer to CHANGELOG.md for details.
v3.0.3Compare Source
Please refer to CHANGELOG.md for details.
v3.0.2Compare Source
Please refer to CHANGELOG.md for details.
v3.0.1Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0: One PieceCompare Source
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:
@vue/reactivitymodule 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
.vuefiles):<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 vuewill still install Vue 2.x andnpm install vue@nextwill 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.
v3.0.0-rc.13Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-rc.12Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-rc.11Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-rc.10Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-rc.9Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-rc.8Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-rc.7Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-rc.6Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-rc.5Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-rc.4Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-rc.3Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-rc.2Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-rc.1Compare Source
RC announcement post
Please refer to CHANGELOG.md for details.
v3.0.0-beta.24Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.23Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.22Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.21Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.20Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.19Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.18Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.17Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.16Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.15Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.14Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.13Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.12Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.11Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.10Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.9Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.8Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.7Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.6Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.5Compare Source
Please refer to CHANGELOG.md for details.
v3.0.0-beta.4Compare Source
v3.0.0-beta.3Compare Source
v3.0.0-beta.2Compare Source
v3.0.0-beta.1Compare Source
v3.0.0-alpha.13Compare Source
v3.0.0-alpha.12Compare Source
v3.0.0-alpha.11Compare Source
v3.0.0-alpha.10Compare Source
v3.0.0-alpha.9Compare Source
v3.0.0-alpha.8Compare Source
v3.0.0-alpha.7Compare Source
v3.0.0-alpha.6Compare Source
v3.0.0-alpha.5Compare Source
Basic SSR support is now provided via
@vue/compiler-ssrand@vue/server-renderer. Note that some features of SSR is still WIP - namely Suspense support and hydration mismatch handling.Note that to enable hydration on the client, use
createSSRAppinstead ofcreateAppto create your app instance (separate imports allows hydration logic to be tree-shakeable for apps that do not require hydration).v3.0.0-alpha.4Compare Source
v3.0.0-alpha.3Compare Source
v3.0.0-alpha.2Compare Source
v3.0.0-alpha.1Compare Source
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) in timezone America/New_York, Automerge - Monday through Friday ( * * * * 1-5 ) in timezone America/New_York.
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.