Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use async-to-generator even when regenerator is enabled #10839

Merged
merged 1 commit into from Dec 9, 2019
Merged

Use async-to-generator even when regenerator is enabled #10839

merged 1 commit into from Dec 9, 2019

Commits on Dec 8, 2019

  1. Use async-to-generator even when regenerator is enabled 

    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
    @nicolo-ribaudo
    nicolo-ribaudo committed Dec 8, 2019
    Copy the full SHA
    b790d79 View commit details
    Browse the repository at this point in the history