npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

async-ctrl

v1.0.0

Published

Controller of consecutive or concurrent execution of a sequence of asynchronous operations

Downloads

5

Readme

Controller of consecutive or concurrent execution of a sequence of asynchronous operations

Example

var AsyncCtrl = require("async-ctrl");
var initialValue = 1;
var scopeObject = {};
AsyncCtrl([
    function(success, failure, value, scope) {
        setTimeout(function() { 
            success(value * 2);
        }, 1500);
    },
    [function(success, failure, value, scope) {
        setTimeout(function() { 
            if ( ++scope.successes$ === 2 )
                success(value * 3);
        }, 2500);
    }, function(success, failure, value, scope) {
        setTimeout(function() { 
            if ( ++scope.successes$ === 2 )
                success(value * 2);
        }, 1500);
    }, function(success, failure, value, scope) {
        setTimeout(function() { 
            failure(-value);
        }, 3500);
    }],
])(initialValue, scopeObject)
    .onSuccess(function(value) {
        console.log(value); //6
    })
    .onFailure(function(error) {
        console.error(error);
    });

Usage

The first step is defining the task list. The entry point function (AsyncCtrl) accepts this list and return controller's constructor for this list and its invocation starts the execution. That constructor accepts two optional arguments: initial value for the first task and object meant to imitate the inner scope of the tasks. The constructor returns controller's instance with onSuccess(handler) and onFailure(handler) methods for assigning the execution outcome handlers. The fact of the handlers' invocations is independent of the time they were assigned. It is possible to terminate the further execution by calling the failure(error) method of the instance in which case the failure handlers will be invoked. Ultimately only one group of handlers will be triggered.

Convention

The list of tasks is an array containing consecutively executed tasks. Each of these tasks is a function or an array of functions being invoked simultaneously. Successfulness is reported via the first argument of the function and an error via the second one. For each task only the first such report takes effect. Once a successful result is reported the execution process proceeds to the next task or is terminated in case of an error. Each function receives the successful result of the previous task via the third argument and the scope object via the fourth argument. Before the execution of the next task begins the attribute values$ of the scope object is assigned to an empty array and the attributes successes$ and failures$ are assigned to a value 0 which enables communications between concurrently executed functions. The last task's successful result or an error report will be passed to the appropriate outcome handlers.