Upgraded to babel 7 #8948
Merged
Upgraded to babel 7 #8948
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vikr01
force-pushed
the
feature/babel-7
branch
from
fb13c58 to
371f687
Compare
|
Vue 3 will use TypeScript. |
|
@Shyam-Chen Why will Vue3.X decide to use TypeScript ? What is the pros and cons? |
|
Thanks! |
f2009
pushed a commit
to f2009/vue
that referenced
this pull request
Jan 25, 2019
aJean
pushed a commit
to aJean/vue
that referenced
this pull request
Aug 19, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
The PR fulfills these requirements:
devbranch for v2.x (or to a previous version branch), not themasterbranchOther information:
Upgrades all
babeldependencies to work withbabelv7.babel-preset-flow-vueis not compatible, so I've recreated it in the.babelrc.jsdirectly.Also changed the
jasmine.jsonfiles tojasmine.jsso thatrequire.resolvecan be used instead of assuming wherenode_modulesare. With things likeplug'n'playcoming to yarn, this is a necessary change.