async-caf - npm Package Compare versions

Comparing version 3.0.5 to 3.0.6

dist/caf.js

 /*! caf.js
-	v3.0.5 (c) 2018 Kyle Simpson
+	v3.0.6 (c) 2018 Kyle Simpson
 	MIT License: http://getify.mit-license.org
@@ -4,0 +4,0 @@ */

package.json

 {
 	"name": "async-caf",
-	"version": "3.0.5",
+	"version": "3.0.6",
 	"description": "Wrapper for generators as cancelable async functions",
@@ -21,9 +21,10 @@ "main": "./dist/caf.js",
 		"coveralls": "~3.0.0",
-		"qunitjs": "~2.4.1"
+		"qunit": "~2.4.1"
 	},
 	"repository": "getify/caf",
 	"keywords": [
-		"fp",
-		"functional programming",
-		"async"
+		"async",
+		"promises",
+		"generators",
+		"cancelation"
 	],
@@ -30,0 +31,0 @@ "bugs": {

README.md

@@ -234,3 +234,3 @@ # Cancelable Async Functions (CAF)
 
-As illustrated earlier, it's totally OK and intended that a single cancelation token `signal` be shared across all the functions in **one** chain of calls (`A` -> `B` -> `C`). But reusing the same token **across two or more chains of calls** (`A` -> `B` -> `C` and `D` -> `E` -> `F`) is asking for trouble.
+As illustrated earlier, it's totally OK and intended that a single cancelation token `signal` be shared across all the functions in **one** chain of calls (`A` -> `B` -> `C`). But reusing the same token **across two or more chains of calls** (`A` -> `B` -> `C` ***and*** `D` -> `E` -> `F`) is asking for trouble.
 
@@ -237,0 +237,0 @@ Imagine a scenario where you make two separate `fetch(..)` calls, one after the other, and the second one runs too long so you cancel it via a timeout:

scripts/node-tests.js

@@ -18,3 +18,3 @@ #!/usr/bin/env node
 
-global.QUnit = require("qunitjs");
+global.QUnit = require("qunit");
 
@@ -21,0 +21,0 @@ require("../tests/qunit.config.js");

No alert changes

Improved metrics

Total package byte prevSize

38917

increased by0.03%

No dependency changes