task-serializer - npm Package Compare versions

Comparing version 1.0.0 to 1.0.1

package.json

		{
		"name": "task-serializer",
		"version": "1.0.0",
		"version": "1.0.1",
		"description": "Serialize tasks/promises for integrated control. Option for limiting number of concurrent tasks.",
		@@ -5,0 +5,0 @@ "main": "index.js",

README.md

		@@ -7,5 +7,4 @@ copyright 2020 craigphicks ISC license
		# Outline
		The `TaskSerializer` module can serialize tasks/promises for integrated control - Tasks/promises can be added immediately as they are produced and placed in a pipline to be made available to a consumer when they have resolved and when the consumer is ready.
		The `TaskSerializer` module can serialize tasks/promises for integrated control - Tasks/promises can be added immediately as they are produced and then be made available to a consumer when they have resolved and the consumer is ready to read them.
		Optionally, the number of concurrently running tasks are limited to a user parameter. In that special case, only functions (and their args) may be added, and function will be executed when a space is available. Trying to add promises will throw an Error.
		Errors are prioritized to be presented before the results on normally returning tasks. (Except for the case of `WaitAll.waitAllSettled`.)
		All rejected tasks/promises are managed so that they don't throw unhandled rejections.
		@@ -42,2 +41,4 @@ The are 4 different classes exported from the module:

		Read-buffered classes prioritize rejected-values over resolved-values, and pass the rejected-values first whenever both are availabe. The exception to this rule is `WaitAll.waitAllSettled()`, which transforms rejected-values into resolved-values.

		# Usage examples
		@@ -44,0 +45,0 @@

New alerts