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
I'm experimenting with the usage-pure mode to polyfill. The debug output from the plugins seems to indicate that no polyfills are applied - every source file has a debug output of: Based on your code and targets, the corejs3 polyfill did not add any polyfill. Based on your code and targets, the regenerator polyfill did not add any polyfill.
However, when I look at the output JS, I can see that polyfills (such as Promise) have been applied (as I would expect). How come none of the applied polyfills are mentioned in the debug output? Am I missing them being applied elsewhere or is this a quirk of the new polyfills plugins? Thanks!
For information:
I have a browserslist config in package.json of > 0.25%, not dead, which gives a targets list of:
Worth mentioning that switching to using the basic preset-envuseBuiltins: "usage" (without the polyfill plugins) outputs the applied polyfills I would expect in it's debug - so maybe the debug output is incorrect in the polyfill plugins?
Hi,
I'm experimenting with the
usage-pure
mode to polyfill. The debug output from the plugins seems to indicate that no polyfills are applied - every source file has a debug output of:Based on your code and targets, the corejs3 polyfill did not add any polyfill.
Based on your code and targets, the regenerator polyfill did not add any polyfill.
However, when I look at the output JS, I can see that polyfills (such as Promise) have been applied (as I would expect). How come none of the applied polyfills are mentioned in the debug output? Am I missing them being applied elsewhere or is this a quirk of the new polyfills plugins? Thanks!
For information:
I have a browserslist config in package.json of
> 0.25%, not dead
, which gives a targets list of:My Babel config looks like this:
The text was updated successfully, but these errors were encountered: