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 🙏

© 2026 – Pkg Stats / Ryan Hefner

promise-qu

v0.0.2

Published

Execute Promises sequentially

Readme

Promise Qu

Promise Qu uses recursion to sequentially execute an array of Promises. The queue will wait until the current Promise is resolved before moving on to the next item.

Why use Promise Qu?

If you have an array of Promises that need to wait for the previous one to resolve before continuing.

Usage

In order to set up a basic queue you can use the following code snippet. In the example below a new queue instance is created and Promise jobs are pushed to the queue. Although there is a setTimeout in the first job, it will wait for this to finish before moving on to job-2 and job-3.

add(() => ...) will push a Promise to the queue.

start() will begin the execution of each job in the queue, this returns a Promise.

const PromiseQu = require('./src');

const isQueueStoppedByError = false;
const q = new PromiseQu(isQueueStoppedByError);

q.add('job-1', () => new Promise((resolve, reject) => {
    setTimeout(() => {
        reject(1);
    }, 1000);
}));

q.add('job-2', () => new Promise((resolve, reject) => {
    resolve(2);
}));

q.add('job-3', () => new Promise((resolve, reject) => {
    resolve(3);
}));

q.start()
    .then(res => console.log(res))
    .catch(error => console.log('ERROR IN QUEUE', error));

Each job has the following structure:

{
    "key": "job-1",
    "job": "<YOUR_FUNCTION>",
    "status": "<ERROR | NOT_STARTED | PENDING | SUCCESS>"
}

The flag isQueueStoppedByError will stop the Queue from continuing to execute if it is set to true. If false it will continue on and push the error to an errors array to view once everything is complete. The end response will look like:

{
    "errors": [
        {
            "result": 1,
            "key": "job-1",
            "status": "ERROR"
        }
    ],
    "success": [
        {
            "key": "job-2",
            "result": 2,
            "status": "SUCCESS"
        },
        {
            "key": "job-3",
            "result": 3,
            "status": "SUCCESS"
        }
    ]
}