node-vasync
node-vasync copied to clipboard
utilities for observable asynchronous control flow
It's a programmer error (i.e., a violation of the intended API) for a vasync pipeline stage to invoke its completion callback more than once. It would be nice if vasync...
When running functions using `vasync.parallel` can we make the guarantee that the functions will be executed in the order they are passed in? I know that they will be executed...
As a result of the work on issue-32, the underlying implementations for pipeline() and waterfall() were refactored. During this refactor, a bug was introduced in which the pipeline() function does...
Since the filter calls went in, we have not bumped the version nor have we modified changes.md. We wish to do this.
Since pipeline stages tend to be logically important steps, they're a natural place to record timestamps. By having vasync record high-resolution timestamps for the start and completion of each operation...
Some mockup libraries (like testdouble) makes it easy to turn synchronous code into synchronous code (for easier testing). By default, vasync breaks synchronous flow by calling callbacks inside a `setImmediate`...
this allows for a level of indentation to be dropped, which can be useful when trying to stay within 80 columns for source files that make complex use of vasync...
See SAPI-266 for occasion where this is really wanted, but basically in general where the array of inputs _can_ grow large, you always want a limitation on concurrency. The programmer...
When forEachParallel expand task function from arguments array , it losts function name, even the task function has name. Please see vasync.js line 135. It will be hard to debug....
I keep running into a situation where I don't need to continue a pipeline or a waterfall because a certain condition has been met. One way to handle this is...