[refactor] es modules, no global polution

[Andarist]

this would mean breaking change

So basically what I would like to do (I can prepare PRs) is to refactor packages. Changes should be pretty straightforward and would include:

• including 2 distributions of regenerator-runtime, both commonjs and es
• stop auto pollution of global object - we can distribute also umd bundle if somebody needs it
• rewrite regenerator-transform to add an import for regenerator-runtime to the transformed module if needed - we can support old way (using global) with an option to the transform

Benefits:

• no more weirdo code ;)
• tree-shakability of the regenerator-runtime - when one uses i.e. only normal generators then parts about async functions could be tree-shaken easily

I think the module is stable and this would make for a great v1 release.

[benjamn]

Please feel free to submit a PR for this!

[utrolig]

Any update on this? With regenerator-runtime auto pollutes the global-scope, there's no way to achieve a 100% pure polyfilling without scope pollution as described in https://github.com/babel/babel-polyfills/issues/59