regenerator icon indicating copy to clipboard operation
regenerator copied to clipboard

Source transformer enabling ECMAScript 6 generator functions in JavaScript-of-today.

Results 80 regenerator issues
Sort by recently updated
recently updated
newest added

Hey, So in your source you check for [AwaitArgument ](https://github.com/facebook/regenerator/blob/2c50f3b8b2b1215a98a04da8a4d30c75e9bcdc52/packages/regenerator-runtime/runtime.js#L144) that can be created only by [awrap](https://github.com/facebook/regenerator/blob/2c50f3b8b2b1215a98a04da8a4d30c75e9bcdc52/packages/regenerator-runtime/runtime.js#L129) function, but it turns out newest babel with default setup doesn't wrap result...

Based on the discussion at https://github.com/facebook/regenerator/issues/236, `await` should always defer. However, I seem to have found bug? The following example behaves as if the `await null` line doesn't defer, causing...

What about transpiling to es2015? Is it in plans or should [transform-async-to-generator](http://babeljs.io/docs/plugins/transform-async-to-generator/) be preferred for that?

I've got the following simple code (compiled with Babel+Regenerator) that causes the browser to lock up, but I thought that `await`ing inside the while loop would free the CPU for...

Consider this code: ``` js const iterable = { [Symbol.iterator]: () => ({ next: () => ({ value: 1 }), throw: undefined, return: () => ({ done: !console.log(".return()") }) })...

A lot of noise when minifying browserified bundle (more than half are from dependencies though): ``` WARN: Dropping unused function forEach [dist/regenerator.bundle.js:2833,9] WARN: Side effects in initialization of unused variable...

The following code: ``` javascript (function *() { with (yield) { } }) ``` crashes regenerator.

I'm now operating under an environment that supports generators out of the box. I'd still like to convert my async functions however. Babel has asyncToGenerator for this, but that seems...

This async function tries to return an array of values concurrently resolved by different Promises (i.e. an equivalent for `Promise.all()`): ``` js async function demo() { try { let things...

x-post from https://github.com/babel/babel/issues/590 By abrupts, I am referring to `break`, `continue`, `throw`, `return`, etc. For example, if you compile the following: ``` function *foo() { for (;;) { bar() break...

enhancement