Support fully disabling Node polyfills perhaps?

This is kind of half feature request half bug report 😛

1.5.x introduced ‘setImmediate’ pollyfilling, which is great, but in our case it was kind of a regression because it meant when we updated, we had a new rewrite that polyfilled setImmediate calls that were previously not rewritten. That caused some of our tests started failing because of slight timing differences between the new setImmediate polyfill and Q own internal polyfill.

I’ll just set setImmediate: false now, but I’m now slightly concerned about updated in the future silently starting to inject polyfills that I don’t expect. Not necessarily the end of the world, but we try to track all 3rd-party code that we package and distribute, and this would have probably been missed if not for the test failures it caused.


Author: Fantashit

1 thought on “Support fully disabling Node polyfills perhaps?

  1. I would like to be able to disable the node polyfills as well. I would rather have my code depend directly on the polyfill, since we want to avoid situations where version bumping a build tool (webpack) can impact the stability of running production code or introduce potential security flaws because code is getting automatically injected. Our team is currently enforcing this through code reviews, but I’d rather be able to disable this feature entirely.

Comments are closed.