[BUGFIX beta] Update dependencies to use Babel 6. #4937
Merged
Conversation
This file contains 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
|
Looks like there are some dependency errors in the build but we should be able to fix those and get this merged in before the |
In ember-cli@2.13 we intend to ship only one version of babel by default (though having multiple versions does work perfectly fine). These deps have just been released, the only breaking change (to them) was bumping the min engine version to Node 4 which we have already done here.
|
I tweaked the |
|
Sweet, looks like that was the issue. @bmac - Passing now. |
|
Thanks @rwjblue. |
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.
In ember-cli@2.13 we intend to ship only one version of babel by default (though having multiple versions does work perfectly fine).
These deps have just been released, the only breaking change (to them) was bumping the min engine version to Node 4 which we have already done here.
@bmac - Is it possible to land this into 2.13.0 before shipping it?