Update ember-cli to v2.3.0 #4188
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
The diff should basically be the same as this one: ember-cli/ember-addon-output@v1.13.12...v2.3.0 Also, since loader.js is a npm module now, the custom build pipeline for the globals build has been adapted, so the loader.js is now read from the corresponding folder in the node_modules directory.
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.
The diff should basically be the same as this one:
ember-cli/ember-addon-output@v1.13.12...v2.3.0
Also, since loader.js is a npm module now, the custom build pipeline for
the globals build has been adapted, so the loader.js is now read from
the corresponding folder in the node_modules directory.
There is a warning now for
vendor-prefixbeing deprecated. It is used in the in-repo-addon here, so theENABLE_OPTIONAL_FEATURESworks correctly. I will try to take a look in the future, but I think this can be tackled once this PR is merged as well...