Update vue-cli monorepo to v3.12.1 #54
Open
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.10.0->3.12.13.10.0->3.12.13.10.0->3.12.1Release Notes
vuejs/vue-cli (@vue/cli-plugin-babel)
v3.12.1Compare Source
Regarding recent patch releases of Vue CLI v4, we are not fixing bugs in v4 itself, but for v3 compatibility actually (to be more specific, for the
vue add routerandvue add vuexcommands in the older CLI versions, user projects are not likely affected). We still recommend all users to upgrade to v4 early.This is because we've made a mistake in implementing the version check mechanism of core plugins in v3. As we expect to bring users the latest and best practices for their projects, we always use the latest versions of the core plugins for scaffolding. This, however, became a burden when we bump the major versions. During the RC phase, the version check logic wasn't triggered, thus we failed to spot this problem early enough.
Luckily, few breaking changes have been made in v4 regarding the scaffolding part, so most users are not affected.
The main issues are due to the changed locations of
routerandvuextemplates. But as the usage varies (scaffolding via Vue CLI UI / command line; calling CLI v4 in v3 projects; calling CLI v3 in v4 projects, etc.), it took us several patches to fully address these issues. We are now also releasing this patch version in v3 so that users who are not confident enough to upgrade their workflow to v4 can have a more backward-compatible CLI to use.🐛 Bug Fix
@vue/cliCommitters: 1
v3.12.0Compare Source
🚀 New Features
@vue/cli-service🐛 Bug Fix
@vue/cli-service@vue/cli-shared-utils@vue/clitestcommand from generated README (@cexbrayat)📝 Documentation
@vue/cliCommitters: 6
v3.11.0Compare Source
🚀 New Features
@vue/cli-service--inline-vueflag forbuildcommand to avoid externalization of Vue in lib & wc mode (@romansp)@vue/cli-plugin-babel,@vue/cli-plugin-e2e-cypress,@vue/cli-plugin-e2e-nightwatch,@vue/cli-plugin-eslint,@vue/cli-plugin-pwa,@vue/cli-plugin-typescript,@vue/cli-plugin-unit-jest,@vue/cli-plugin-unit-mocha,@vue/cli-shared-utilsvue add(@sodatea)🐛 Bug Fix
@vue/cli-plugin-eslint,@vue/cli-ui@vue/cli-serviceexternalsconfig correctly, supports array (@sodatea)@vue/cli-plugin-unit-jest,@vue/cli-plugin-unit-mocha**/tests/**subfolders (@LinusBorg)@vue/cli-shared-utilsresolvePluginIdshould correctly resolve@vue/cli-service(@sodatea)📝 Documentation
🏠 Internal
@vue/cli-ui-addon-webpack,@vue/cli-ui🔨 Underlying Tools
@vue/cli-service@vue/cli-plugin-babel,@vue/cli-plugin-eslint,@vue/cli-plugin-pwa,@vue/cli-plugin-typescript,@vue/cli-serviceCommitters: 9
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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.