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 🙏

© 2025 – Pkg Stats / Ryan Hefner

await-limit

v0.1.3

Published

Easy control flow for running lots and lots of async functions with a concurrency limit.

Downloads

198

Readme

Await Limit

Easy control flow for running lots and lots of async functions with a concurrency limit.

Designed to have a nicer API than some of the other similar libraries which perform throttling and limiting.

Ideally it should be a drop-in replacement for Promise.all. However, this is not possible - the promises themselves must be wrapped in a function for it to be effectively batched.

Usage

const limit = require('await-limit');

.all

Runs all of the provided async functions as fast as possible up to a provided concurrency limit.

Resolves to an array of the value resolved by each task.

const concurrency = 2;

const results = await limit.all(concurrency, [
	async () => {},
	async () => {},
	async () => {},
	async () => {},
	async () => {},
]);
const concurrency = 5;

const userIds = ['123', '456' /* lots more items */];

const results = await limit.all(concurrency, tasks.map(userId => async () => doDatabaseUpdate({ userId })));

.map

Runs the provided async function against each item in a provided array as fast as possible up to a provided concurrency limit.

Resolves to an array of the values resolved by each invocation of the function.

const concurrency = 25;

const userIds = await getUsers();

const result = await limit.map(concurrency, userIds, async userId => {
	const pref = await getUserPreference('marketingEmailConsent');
	if (!pref) return false;

	await sendMarketingEmail(userId);

	return true;
});

.filter

Runs the provided async function against each item in a provided array as fast as possible up to a provided concurrency limit.

Resolves to a new array where each item from the original array is omitted if the resolved value of the function is falsy.

const concurrency = 25;

const userIds = await getUsers();

const result = await limit.filter(concurrency, userIds, async userId => {
	const pref = await getUserPreference('marketingEmailConsent');
	return pref;
});

.each

Runs each async function one after the other and collects the results.

const results = await limit.each([
	async () => {
		// First operation
		return 'foo';
	},

	async () => {
		// First operation
		return 'bar';
	},
]);

console.log(results); // [ 'foo', 'bar' ]

Error handling

This library handles errors quite differently to Promise.all.

It will continue to invoke all of the provided tasks until completion, and collect any error states as it goes.

Afterwards, if the errors array has length, it will throw.

{
	message: "AwaitLimit encountered errors",
	details: [
		undefined, // Tasks which did not error
		undefined,
		{} // Error from a failed task
	],
}

if this is not desirable in your use case, you must make sure to handle errors inside the tasks, and then populate the result array with the data you need to evaluate success/failure.