babel

Author SHA1 Message Date

Author	SHA1	Message	Date
Nicolò Ribaudo	2884bac44b	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	2019-12-09 16:54:25 -05:00
Nicolò Ribaudo	861844761f	[preset-env] Don't use async-to-generator when already using re… (#9481 ) * [preset-env] Don't use async-to-generator when already using regenerator * Add tests * Update fixtures	2019-11-04 22:53:53 +01:00

Nicolò Ribaudo

2884bac44b

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

2019-12-09 16:54:25 -05:00

Nicolò Ribaudo

861844761f

[preset-env] Don't use async-to-generator when already using re… (#9481 )

* [preset-env] Don't use async-to-generator when already using regenerator

* Add tests

* Update fixtures

2019-11-04 22:53:53 +01:00

2 Commits