Stock vue template has a Babel error

[gorbypark]

🐛 bug report

Description of the problem

The stock vue template throws an error. [BABEL] /src/main.js: Invalid Option: corejs is not a valid top-level option. Maybe you meant to use 'targets'? (While processing: "base$0$0")

Link to sandbox: stock vue template

Your Environment

Software	Name/Version
Сodesandbox	PROD-1553607023-33a33af1a
Browser	Chrome 73
Operating System	macOS

[AndreasCag]

Same issue. Today I published article about Vue.js form validations and found that all code examples didn't work.

I found fast fix:
Replace this in package.json

    "@vue/cli-plugin-babel": "^3.4.0",
    "@vue/cli-plugin-eslint": "^3.4.0",
    "@vue/cli-service": "^3.4.0",

To this

    "@vue/cli-plugin-babel": "3.4.0",
    "@vue/cli-plugin-eslint": "3.4.0",
    "@vue/cli-service": "3.4.0",

[LeeChar]

Same issue. Today I published article about Vue.js form validations and found that all code examples didn't work.

I found fast fix:
Replace this in package.json

    "@vue/cli-plugin-babel": "^3.4.0",
    "@vue/cli-plugin-eslint": "^3.4.0",
    "@vue/cli-service": "^3.4.0",

To this

    "@vue/cli-plugin-babel": "3.4.0",
    "@vue/cli-plugin-eslint": "3.4.0",
    "@vue/cli-service": "3.4.0",

It's starting to work properly.but why？

[lbogdan]

We're looking into this!

[CompuIves]

Hey! I found the issue, it's related to a recent new release of @vue/cli-plugin-babel. Some new configuration parameters were given to @babel/preset-env since 3.5.2(vuejs/vue-cli@156ef21), but our @babel/preset-env installed in the sandbox was too old and threw a validation error.

I installed a new version of preset-env in the sandbox as a temporary solution, that should be live in ~15min. A long-term solution would be to either add support for lockfiles or to use the babel-preset-env provided by @vue/cli.

[CompuIves]

The fix is live and the issue should be resolved! Sorry for the inconvenience, I'll make sure to run our CI check periodically and find a better solution for the env preset.

Thanks for the workaround @AndreasCag, that helped a lot with pinpointing the issue!

Let me know if it's fixed for you, then we can close the issue.

[lbogdan]

For future reference, the fix commit is 7cb89e2 .

[lbogdan]

Closing this, as the lack of feedback signals me this has been solved. Please reopen if that's not the case.