Avoid multiple babel-polyfill loaded #29
Merged
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.
I think this patch will actually fix #16. Just explain again in the following
for the users who wrote webpack with es6 and there are two way to run
first is using
babel-node
, second isnode --harmony
and addrequire('babel/register');
at entry point. For these both condition, it will loadbabel/polyfill
at first in runtime, so we need add a flag to avoidbootstrap-loader
to loadbabel/polyfill
again.So I thinks this patch can fix
ERROR in only one instance of babel-polyfill is allowed
issue correctly.btw, I think I can make the code more clean in the beginning of
src/bootstrap.loader.js
, if I have free time, I will do another PRThanks