Skip to content
Branch: master
Find file History
nicolo-ribaudo and JLHwung Use `async-to-generator` even when `regenerator` is enabled (#10839)
While it isn't technically needed because regenerator already handles
async functions, it doesn't play well with the Promise detection logic
used by @babel/preset-env's useBuiltIns and @babel/transform-runtime.

The plugin exclusion logic isn't removed, because
1) it will be useful when merging @babel/preset-modules
    into @babel/preset-env
2) if/when regenerator will support injecting a custom promise,
    we can enable this optimization again
Latest commit 2884bac Dec 9, 2019


A Babel preset for each environment.

See our website @babel/preset-env for more information or the issues associated with this package.


Using npm:

npm install --save-dev @babel/preset-env

or using yarn:

yarn add @babel/preset-env --dev
You can’t perform that action at this time.