regenerator-runtime - npm Package Compare versions

Comparing version 0.11.1 to 0.12.0

package.json

@@ -5,3 +5,3 @@ {
   "description": "Runtime for Regenerator-compiled generator and async functions.",
-  "version": "0.11.1",
+  "version": "0.12.0",
   "main": "runtime-module.js",
@@ -8,0 +8,0 @@ "keywords": [

runtime.js

@@ -171,18 +171,10 @@ /**
           // the .value of the Promise<{value,done}> result for the
-          // current iteration. If the Promise is rejected, however, the
-          // result for this iteration will be rejected with the same
-          // reason. Note that rejections of yielded Promises are not
-          // thrown back into the generator function, as is the case
-          // when an awaited Promise is rejected. This difference in
-          // behavior between yield and await is important, because it
-          // allows the consumer to decide what to do with the yielded
-          // rejection (swallow it and continue, manually .throw it back
-          // into the generator, abandon iteration, whatever). With
-          // await, by contrast, there is no opportunity to examine the
-          // rejection reason outside the generator function, so the
-          // only option is to throw it from the await expression, and
-          // let the generator function handle the exception.
+          // current iteration.
           result.value = unwrapped;
           resolve(result);
-        }, reject);
+        }, function(error) {
+          // If a rejected Promise was yielded, throw the rejection back
+          // into the async generator function so it can be handled there.
+          return invoke("throw", error, resolve, reject);
+        });
       }
@@ -189,0 +181,0 @@ }

No alert changes

Worsened metrics

Total package byte prevSize

26075

decreased by-2.43%

Lines of code

648

decreased by-1.22%

No dependency changes