core-js@3 contains queueMicrotask polyfill.
queueMicrotask added to Node.js 11 as an experimental feature.
On getting queueMicrotask global property on Node.js 11, emitted an ExperimentalWarning. Without a special handler, this warning pollutes the global output.
Even this method not used, core-js detect it by getting this property. So even import of core-js@3 pollutes the global output by this warning.
core-js is a quite popular library, so after updating to stabe core-js@3, pollution of the global output will cause too many problems.
Any ideas what should I do for preventing this problem? process.on('warning', ..)? But it does not look like a solution for a library.
core-js@3containsqueueMicrotaskpolyfill.queueMicrotaskadded to Node.js 11 as an experimental feature.On getting
queueMicrotaskglobal property on Node.js 11, emitted anExperimentalWarning. Without a special handler, this warning pollutes the global output.Even this method not used,
core-jsdetect it by getting this property. So even import ofcore-js@3pollutes the global output by this warning.core-jsis a quite popular library, so after updating to stabecore-js@3, pollution of the global output will cause too many problems.Any ideas what should I do for preventing this problem?
process.on('warning', ..)? But it does not look like a solution for a library.