babel-preset-latest deprecation warning at npm install #420
Comments
|
Hello! |
|
I'm not sure I understand. As noted in the issue, this warning is immediately after the very first npm install of the vue-cli package, not when creating a new skeleton with any particular template. In other words, the first experience a new user has when installing vue-cli for the first time is a deprecation warning...nothing to do with any specific template. The steps to replicate are as indicated in the issue: simply try to do a fresh install with "npm install -g vue-cli"... |
|
Ups, closed a bit too fast. That warning appear because of a dependency in
vue-cli but the problem should be fixed somewhere else. I'll check it once
I'm home. It's probably a Vue preset
…On Fri, 31 Mar 2017, 15:44 John Kole, ***@***.***> wrote:
I'm not sure I understand. As noted in the issue, this warning is
immediately after the very first npm install of the vue-cli package, not
when creating a new skeleton with any particular template. In other words,
the first experience a new user has when installing vue-cli for the first
time is a deprecation warning...nothing to do with any specific template.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#420 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAoicZQ2CZBLuAdSVwJOsIRZ_ZHjctwaks5rrQM9gaJpZM4MupgQ>
.
|
|
Just got this today -- is there any blockers to updating |
This was referenced Dec 28, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
Doing npm install -g vue-cli gives:
npm WARN deprecated babel-preset-latest@6.24.0: 💥 preset-latest accomplishes the same task as babel-preset-env. 🙏 Please install it with 'npm install babel-preset-env --save-dev'. '{ "presets": ["latest"] }' to '{ "presets": ["env"] }'. For more info, please check the docs: http://babeljs.io/docs/plugins/preset-env 👌. And let us know how you're liking Babel at @babeljs on 🐦
The text was updated successfully, but these errors were encountered: