Breaks if regenerator-runtime is not required by Babel targets

[raido]

Application will crash if ember-maybe-import-regenerator has determined based on config/targets.js browsers that regenerator runtime is not required but somehow -cancelable-promise-helpers still depends on regenerator.

Workaround for now

https://www.npmjs.com/package/regenerator-runtime

yarn add/npm i regenerator-runtime

// ember-cli-build.js

if (isProduction) { // If your production targets are different from development ones
   app.import(require('regenerator-runtime/path').path, { prepend: true });
}

[maxfierke]

I think this is likely an issue with the babel or ember-cli-babel setup in your app (or potentially ember-maybe-import-regenerator), as we don't use or enforce regenerator runtime directly within ember-concurrency.

For example, you may need to add exclude: ['@babel/plugin-transform-regenerator']; to your ember-cli-babel babel config.

[raido]

It seems so actually, I found out which of the browserlist queries caused it. I have explicit query for not Safari < 10 - and that blows it up.

This query also blows up ember-cli-test-loader and few other things. But yes, ember-concurrency here is not the reason.