You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
runtime.js currently caches the values of Symbol.iterator, Symbol.asyncIterator and Symbol.toStringTag when it is loaded (here).
This can cause issues when regenerator-runtime is loaded before the Symbol polyfills. Here is an example of Babel build that fails running on IE11 due to the order of the imports:
I did create an issue in Babel's repository. However, since regenerator is used by more than just Babel, and that this behavior can also affect other tools, I believe it would be better for regenerator-runtime to read the Symbol values wen invoked rather than when loaded. What do you think ?
The text was updated successfully, but these errors were encountered:
runtime.js
currently caches the values ofSymbol.iterator
,Symbol.asyncIterator
andSymbol.toStringTag
when it is loaded (here).This can cause issues when
regenerator-runtime
is loaded before theSymbol
polyfills. Here is an example of Babel build that fails running on IE11 due to the order of the imports:I did create an issue in Babel's repository. However, since
regenerator
is used by more than just Babel, and that this behavior can also affect other tools, I believe it would be better forregenerator-runtime
to read theSymbol
values wen invoked rather than when loaded. What do you think ?The text was updated successfully, but these errors were encountered: