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

ak-throttled-queue

v1.4.0

Published

throttled queue for async functions

Readme

ak-throttled-queue

Throttled queue for node.js. Async functions only. No guarantee for sync functions.

Example

// autostart false

const ThrottledQueue = require('ak-throttled-queue');

const queue = new ThrottledQueue({
  interval: 1000,
  concurrency: 5,
  autostart: false
});

// note if autostart is false, you cannot await the fn execution if you are in the same scope since this will block
// this below wont work!

const result = await queue.push(async () => {
  return new Promise(resolve =>
    setTimeout(() => {
      resolve('resolved');
    }, 1000)
  );
});

queue.start();

// this will work

const resultPromise = queue.push(async () => {
  return new Promise(resolve =>
    setTimeout(() => {
      resolve('resolved');
    }, 1000)
  );
});

queue.start();

const result = await resultPromise;

// autostart true (default)

const queue = new ThrottledQueue({
  interval: 1000,
  concurrency: 5
});
// this will work

const result = await queue.push(async () => {
  return new Promise(resolve =>
    setTimeout(() => {
      resolve('resolved');
    }, 1000)
  );
});

// queue end with drain = true

const endPromise = queue.end();

// this will throw an error, because queue is in ending state
queue.push(async () => {});

await endPromise;

// this will work, since queue is clean and finished draining
queue.push(async () => {});

// queue end with drain = false (all queued functions will be rejected with an error
const queue = new ThrottledQueue({
  interval: 1000,
  concurrency: 5,
  autostart: false
});
const queueFnPromise = queue.push(async () => {});

await queue.end({ drain: false });

try {
  await queueFnPromise;
} catch (error) {
  console.log(error);
  // > Error: queue stopped, aborting!
}

Commiting

The project uses commitlint so please follow the commit message guidelines there:

commitlint

yarn commit # runs a commit promt with semver conform commit messages

Workflow

Adding new features/fixes

Create a PR with your code to the develop branch. Please take care that your PR title follows the semantic message format

Once your PR is reviewed and approved, merge it via a SQUASH MERGE commit. Please take care that the title of your squash merge commit is a valid semantic message format

Releases

To trigger a new release simply create and merge a PR to the main branch.