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.
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)
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @vue/cli-service (4.5.4 → 4.5.7) · Repo
Release Notes
4.5.7
4.5.6
4.5.5
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 39 commits:
v4.5.7
chore: merge branch 'master' into dev
Update Vercel deployment instructions (#5835)
fix: update the `.vue` file shim for Vue 3 (#5903)
chore: show error message that the `wc` target with Vue 3 isn't supported yet (#5906)
fix: more accurate warning message for missing global peer dependencies (#5871)
docs: add notes on the `vue inspect` command (#3797) [skip ci]
docs: update netlify docs for vue/cli-plugin-pwa (#5847) [skip ci]
fix: incorrectly read Taobao binary mirror configuration. (#5902)
docs: add solution for `yarn link` error (#5884) [skip ci]
fix: shouldn't remove attribute quotes in HTML (#5899)
docs(zh): in build-targets.md add "using vuex" (#5883) [skip ci]
docs: remove mention of Node.js v8 npm workaround, as it's been fixed [skip ci]
fix: respect scope when resolving package metadata (#5892)
docs: fix typo in en.json (#5885) [ci skip]
v4.5.6
fix: skip checking git gpgSign config (#5869)
chore: Merge branch 'dev' into master
v4.5.5
fix: enable some syntax extensions by default for vue script compiler (#5868)
fix: fix duplicate id="app" in Vue 3 project template (#5852)
fix(unit-jest, unit-mocha): generate passing tests when `bare` option is used with router enabled (#5591)
docs(zh): update plugins-and-presets.md (#5844) [ci skip]
chore: fix indentation
perf(ui): improve get folder list to use Promises instead of sync (#3687)
fix: allow turning off theme color tags (#5820)
chore: rename jsx package scope from ant-design-vue to vue (#5831)
docs: change zeit to vercel (#5807) [ci skip]
test: fix test errors
refactor: remove ListFilter logic (#5391)
fix: fix support for Node.js v8 and deprecate it (#5827)
fix: handle GPG sign git config for initial commit (#5823)
docs: update deployment.md (#5815) [ci skip]
fix: strip non-ansi characters from registry config (#5808)
docs: update Node version requirement to address package manager issues (#5811) [ci skip]
fix: do not throw when api.render is called from an anonymous function (#5801)
docs: writeFileSync path was missing api.resolve (#5804) [ci skip]
docs: update cloudbase deploy doc (#5810)
docs: update cloudbase deploy doc (#5805)
👉 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