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

@altano/tiny-async-pool

v3.0.0

Published

Run multiple promise-returning & async functions with limited concurrency using native ES9

Downloads

11,154

Readme

tiny-async-pool

This is an ESM + TypeScript fork of tiny-async-pool by Rafael Xavier de Souza, with some added functionality.

Why?

The goal of this library is to use the native async iterator (ES9), native async functions, and native Promise to implement concurrent/batched work.

What?

doWorkAndYield runs multiple promise-returning & async functions in a limited concurrency pool. It rejects immediately as soon as one of the promises rejects. It calls the iterator function as soon as possible (under concurrency limit). It returns an async iterator that yields as soon as a promise completes (under concurrency limit). For example:

const timeout = (ms) => new Promise((resolve) => setTimeout(() => resolve(ms), ms));

for await (const ms of doWorkAndYield(2, [1000, 5000, 3000, 2000], timeout)) {
  console.log(ms);
}
// Call iterator timeout(1000)
// Call iterator timeout(5000)
// Concurrency limit of 2 reached, wait for the quicker one to complete...
// 1000 finishes
// for await...of outputs "1000"
// Call iterator timeout(3000)
// Concurrency limit of 2 reached, wait for the quicker one to complete...
// 3000 finishes
// for await...of outputs "3000"
// Call iterator timeout(2000)
// Itaration is complete, wait until running ones complete...
// 5000 finishes
// for await...of outputs "5000"
// 2000 finishes
// for await...of outputs "2000"

Usage

$ npm install @altano/tiny-async-pool
import { doWorkAndYield } from "@altano/tiny-async-pool";

ES9 for await...of

for await (const value of doWorkAndYield(concurrency, iterable, iteratorFn)) {
  console.log(value);
}

API

doWorkAndYield(concurrency, iterable, iteratorFn)

Runs multiple promise-returning & async functions in a limited concurrency pool. It rejects immediately as soon as one of the promises rejects. It calls the iterator function as soon as possible (under concurrency limit). It returns an async iterator that yields as soon as a promise completes (under concurrency limit).

concurrency

The concurrency limit number (>= 1).

iterable

An input iterable object, such as String, Array, TypedArray, Map, and Set.

iteratorFn

Iterator function that takes two arguments: the value of each iteration and the iterable object itself. The iterator function should either return a promise or be an async function.

doWork(concurrency, iterable, iteratorFn)

Like doWorkAndYield(...) but with a simpler API. Useful when you don't care about the return value of iteratorFn, such as a worker pool where you do batch file proccessing and the workers produce a side effect instead of returning a value.

For example, a batch file eraser is as simple as:

const eraseFile = (path) => fs.unlink(path);
const eraseFiles = async (files) => doWork(4, files, eraseFile);

It will be enforced that iteratorFn returns Promise<void> when using TypeScript.

License

MIT © Rafael Xavier de Souza MIT © Alan Norbauer