This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
If you are working on a Vue 3 project, this version of Vue CLI comes with the latest beta version of vue-loader, which enables support for the experimental <script setup> syntax.
First, reinstall the latest version of @vue/cli globally.
yarn global add @vue/cli
# OR
npm install -g @vue/cli
Then in the projects, run
vue upgrade
Notable Changes
The polyfill logic for modern mode and web components target has been refactored.
The final browser target is now calculated from the intersection of the user-specified browser target and the minimum browser versions that support modern mode / web component.
This means we can now drop many polyfills that are only used for some obsolete evergreen browsers if you are using the default browserslist target (["> 1%", "last 2 versions", "not dead"]), which will greatly reduce the bundle size of modern mode / web component target.
๐ Bug Fix
@vue/babel-preset-app
#5513 refactor: improve the polyfill importing logic of modern mode (@sodatea)
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the
service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Travis-CI](https://travis-ci.com) are all excellent options.
* If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
* If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you donโt want it to run on every branch, you can whitelist branches starting with `depfu/`.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
All Depfu comment commands
@โdepfu rebase
Rebases against your default branch and redoes this update
@โdepfu recreate
Recreates this PR, overwriting any edits that you've made to it
@โdepfu merge
Merges this PR once your tests are passing and conflicts are resolved
@โdepfu close
Closes this PR and deletes the branch
@โdepfu reopen
Restores the branch and reopens this PR (if it's closed)
@โdepfu pause
Ignores all future updates for this dependency and closes this PR
@โdepfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@โdepfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
Welcome to Depfu ๐
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
โณ๏ธ @โvue/cli (4.3.1 โ 4.5.7) ยท Repo ยท Changelog
Release Notes
4.5.7
4.5.6
4.5.5
4.5.4
4.5.3
4.5.2
4.4.6
4.4.5
4.4.4
4.4.3
4.4.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
๐ No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Travis-CI](https://travis-ci.com) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you donโt want it to run on every branch, you can whitelist branches starting with `depfu/`.Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands