fix: webpack split chunks incompatibility using IIFE #188
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
|
|
|
Without the IIFE you pollute the global namespace. You can also end up with conflicts with other libraries. |
|
Thank you for the response. If the IIFE is set and it interfere with the chunks feature, then is it considered as bug? |
|
Yes that would be would be a bug. The harder question is determining exactly why it is occurring. It most likely means that the dependency graph is wrong. |
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.
Remove IIFE wrapper on standard build since it prevent multiple Webpack entries and/or chunks for working correctly.
This is also one way to ask for confirmation on what is the purpose of IIFE in standard build?
This comment is another way.