Add 'vue update' command
See original GitHub issueWhat problem does this feature solve?
Hello,
The goal of this request is to be able to update a plugin when it’s already installed within a project.
Thanks a lot!
What does the proposed API look like?
If I have installed Apollo client with vue add apollo
, I would like to do vue update apollo
if a new version is out few days after.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Installation | Vue CLI
To install the new package, use one of the following commands. ... npm update -g @vue/cli # OR yarn global upgrade --latest @vue/cli ......
Read more >How to upgrade my global vue-cli install to the latest version?
I, you can directly update your vucli but the best way is to delete the old version and install a new ...
Read more >How to update vue-cli to latest version? - Programming Basic
Uninstall old vue-cli version ... The vue-cli is the older version and the package name is changed from vue-cli to @vue/cli . So...
Read more >Upgrading Vue CLI from Version 2 to 3 - DevCamp
I'm going to walk through two ways to do this. The first way is just typing vue create my-basic-three-app . Now, this is...
Read more >vue upgrade command asks for a plugin and doesn't ... - GitHub
If you use the standalone installer to install yarn and then yarn global add @vue/cli @vue/cli-upgrade , you can use the vue upgrade...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
vue add
also invokes the plugin, so does more thatyarn add
ornpm i
.Sounds fine in theory, and may be a candidate for a future minor release, but I think this should be postponed until 3.0.0 has reached its real release.
I could imagine a thousand things going wrong if somone runs such an update on an existing project, maybe one that has been extesively modified since the plugin was first invoked.
Chances are that the files you intend to update are no longer there, or have been extensively modified by the developer. Adding a new file might overwrite an existing one that the developer added.
I realize that all of these problems exist to a smaller degree when initially invoking a plugin, and they are manageable with some level of care by the plugin author.
But I think we should wait with such a feature until 3.0.0 has matured a bit, we see the patterns that emerge from new plugins, have a guideline for plugin authors in place that recommends best practices and so on.