-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
vue-cli3 warning for core-js version #3695
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Note: this does not affect actual usage because |
I've got this warning too. The warning doesn't help at all and it creates panics. |
It sure does |
no luck
still there
Bruce Chen <[email protected]> 于 2019年3月25日周一 23:17写道:
… If you want to suppress this warning, just specify the corejs version in
your bable.config.js file like below.
presets: ***@***.***/app', {
useBuiltIns: 'usage',
corejs: 2
}]]
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3695 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AQCpm0MhTqxBwTNEh53IbVphUfwxpyeKks5vabuGgaJpZM4cEr0M>
.
|
Fixed in 3.5.2 |
@sodatea To be pedantic, I think it's really fixed in 3.5.3 since the babel downgrade is also necessary. |
@412799755 Thank you very much! |
I'm still struggling a bit with this. The latest version fixed my problems when building locally, but when I run the build commands in our Bitbucket Pipeline or in the Docker image thereof I get the following error:
I have tried to clear the npm cache and checked all versions of the packages. But so far no dice. All help is much appreciated! |
@dotmartin I was meeting the same problem before. I was using |
@dotmartin as a last resort, try to install core-js@2 as the project's dependency. I'm still thinking about how to fully resolve this issue. |
@sodatea thanks, that seems to work just fine! Is there a ticket I can subscribe to for the final fix? |
Version
3.5.1
Environment info
Steps to reproduce
vue create a project
npm run serve
What is expected?
no warning
What is actually happening?
We noticed you're using the
useBuiltIns
option without declaring a core-js version. Currently, we assume version 2.x when no version is passed. Since this default version will likely change in future versions of Babel, we recommend explicitly setting the core-js version you are using via the
c orejs
option.You should also be sure that the version you pass to the
corejs
option matches the version specified in yourpackage.json
'sdependencies
section. If it doesn't, you need to run one of the following commands:
The text was updated successfully, but these errors were encountered: