Fix ES5 output by using only Babel in this case - #587
Merged
Conversation
|
Hi @elsassph Nice! That seems to work. Also tested in full application. |
Closed
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fixes #536 - Lightning Core > 2.11.0 Unsupported on older browsers
ESbuild/Rollup doesn't seem to allow Babel do the transpilation to older browsers. This is a regression which I didn't try exactly narrowing.
This PR forces all the JS transformation to be done through Babel - it still is properly minified and the JS size is about the same size (~432Kb for
lightning.es5.min.js)