Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Command: vue upgrade

See original GitHub issue

Command that should be run inside an existing project with @vue/cli-service present.

Resolve the version to upgrade to.
- vue upgrade [patch|minor|major]: defaults to minor
If already latest, print message and exit
Otherwise, confirm via prompt
Find @vue/cli-service plus all packages in package.json that starts with @vue/cli-plugin-, and bump them to the target upgrade version
Run installDeps - infer package manager from lockfile, if no lockfile, infer from .vuerc, otherwise infer using hasYarn()
Print changelog of upgraded versions

Issue Analytics

State:
Created 5 years ago
Reactions:24
Comments:7 (3 by maintainers)

Top GitHub Comments

2reactions

TheMushrr00mcommented, Jun 13, 2018

Hey there! Is anyone working on this? I want to try to contribute with this project.

0reactions

NiloCKcommented, Aug 1, 2018

What is the current workflow for upgrading one’s vue-cli packages? Is it safe to do a plain yarn upgrade vue-cli-service --latest? I’m currently sitting at 3.0.0-beta.1. What I’m most interested in is getting vue-cli-plugin-babel up to speed so that I can hopefully resolve these sorts of debug / source map issues.

Should I do an upgrade only on vue-cli-plugin-babel?