-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
Adjust documentation for using @vue/babel-preset-app in a non vue-cli environment #1725
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
I'm not sure that I can reproduce a project with the behaviouir you are seeing
|
I created this online project: https://codesandbox.io/s/7w5qrwpxnq
|
Oh, now i get it. Should have read your title more carefully. So you are using the babel preset in an app not created with vue-cli, and had to dig into the yource to learn that you have to set some ENV variables to make it work the way you expect it to. And your request would be that these env variables are documented in that preset's README. Seems sensilbe. :) |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
How to determine core-js3 in @vue/babel-preset-app? I add the 'corejs' option to preset '@vue/app', but it now work. |
@victor71, For now, use @vue/babel-preset-app v4.0.0-alpha.0. It's too much work for us to keep compatibility with both core-js versions, so we only bump the version in a new major release. |
@sodatea Thank you! |
What problem does this feature solve?
Using ts-jest, babel, @vue/babel-preset-app and @babel/preset-typescript" together, causes tests failures even when setting typescript compiler option
"module"
to"commonjs"
and"allowSyntheticDefaultImports"
to"true"
..babelrc
What does the proposed API look like?
Documentation of setting environment variables before running ts-jest.
The text was updated successfully, but these errors were encountered: