Displaying 1 to 10 from 10 results

syncho - Fast and lean abstraction for node Fibers. Easily run asynchronous functions synchronously.

  •    Javascript

syncho is a thin and fast wrapper around fibers for node.js. The API is very similar to node-sync but optimized to reduce overhead (see benchmarks) and in less than 100 lines of code.Pass a function fn to run in a fiber. This is just a shortcut to Fiber(fn).run(). Synchronized functions will throw in case of error so you can use standard try and catch to run your code. All syncho methods need to be run inside a fiber.

ambi - Execute a function ambidextrously (normalizes the differences between synchronous and asynchronous functions)

  •    Javascript

Execute a function ambidextrously (normalizes the differences between synchronous and asynchronous functions). Useful for treating synchronous functions as asynchronous functions (like supporting both synchronous and asynchronous event definitions automatically).Older environments may need Babel's Polyfill or something similar.

taskgroup - Group together synchronous and asynchronous tasks and execute them with support for concurrency, naming, and nesting

  •    Javascript

Group together synchronous and asynchronous tasks and execute them with support for concurrency, naming, and nesting.Older environments may need Babel's Polyfill or something similar.




node.flow - A deadly simple flow control package for node.js

  •    Javascript

The asynchronous nature of javascript is what makes it so powerful. However sometimes you just need to do stuffs synchronously without blocking the event loop. Stuffs like query database in a loop with ids to assemble a hash, compressing a bunch of files in groups and compare with the old ones. You could easily end up with nested callbacks without using a flow control package. With node.flow you can set a work flow doing things one by one or in parallel, wait for all things are done in the parallel tasks to do the next task. You can set some default arguments for all tasks, giving each task its own arguments or pass task results to the next task as its arguments. The following code shows some base usage and the syntax of this package.

flow.js - synchron, asynchron control flow javascript library

  •    Javascript

flow.js is a synchron-asynchron flow control library which runs on node and in browsers. The functionallity of the library is inspired by node-seq (https://github.com/substack/node-seq) and async (https://github.com/caolan/async). The source is written from scratch.

node-twostep - Simple control-flow library for node.js

  •    HTML

Is a simple control-flow library for node.js that makes serial execution, parallel execution and error handling painless. Inspired by step twostep was based on Tim Caswell (step author) gist, but later it was refactored and almost totally rewritten. Twostep follows and extends the ideas behind the step. All steps (functions) passed to the Step will be executed in series. Inside each step this.slot() for wating of async call, this.pass() for passing value to the next step or this.makeGroup() for creating group (for having results grouped to array) can be called.

shortbus - A lightweight flow control module that works like a mini event bus + serial/parallel processor

  •    Javascript

Shortbus is a lightweight data processing/ETL module designed to run asynchronous processes in a seemingly synchronous way. The module acts as a mini service bus. The approach helps developers produce more readable data flow code. Code is cleaner, more structured, and provides a means to avoid callback hell.


gulp-sequence - Run a series of gulp tasks in order

  •    Javascript

Run a series of gulp tasks in order. return a thunk function.

flowa - 🔥Service level control flow for Node.js

  •    Javascript

Check the suggested way to use Flowa with Express.js. Each flow is a set of tasks. It starts by a compound task which is basically a task that groups a set of single or other compound tasks. Single tasks are either async or sync functions that are executed and called by passing an object called context to allow sharing data between tasks and an optional callback function for async tasks that use callbacks instead of promises. Each compound task's sub tasks are executed by a runner that can be a serial execution (default type) or a parallel execution.