fix(webpack): fix webpack for IE 11 support #1344
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
Currently, webpack 5 builds to target es6 by default, which breaks IE 11 since it only supports up to es5. - Changed webpack build target to es5 - Added fallbacks for unused polyfills that webpack 5 drops from webpack 4 - Specified transpilation order to fix an issue with IE where it breaks react components otherwise
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.
Problem
Currently, webpack 5 builds to target es6 by default, which breaks IE 11 since it only supports up to es5. Additionally, webpack 5 drops quite a few polyfills, which triggers warnings to provide fallbacks even if unused. There is also a transpilation issue with react components where IE would break if the transpilation order was incorrect.
Solution