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

promisedip

v1.1.5

Published

Promise pooler to manage concurrency

Downloads

38

Readme

pipeline status coverage report npm version Downloads js-standard-style Commitizen friendly

NOTE: This lib exposes next-gen code ; this means that you might need polyfills in old environments (e.g.: node < 7.6 or IE).

It ships with:

Installation

NPM

npm i -S promisedip
yarn add promisedip

JavaScript module

<script type="module">
  import PromisePool from 'https://unpkg.com/[email protected]/lib/PromisePool.esm.js';
  // …
</script>

Demo

I made a codesandox to visualize the promise pooling (in the console)

API

NB: Everything is TypeScript-friendly

new PromisePool(options)

Usage:

new PromisePool(options: { concurrency: number })

Example

import PromisePool from 'promisedip'

const pool = new PromisePool({ concurrency: 2 })

async function doStuff (): Promise<void> {
  const [
    examplePage,
    wordscapePage,
    wiki,
  ] = await Promise.all([
    // pool will execute the following promises in the correct order respecting the concurrency option provided
    pool.resolve(() => fetch('https://example.com/')),
    pool.resolve(() => fetch('https://wordscape.com/')),
    pool.resolve(async () => {
      const response = await fetch('https://en.wikipedia.org/')
      // … do anything else you need
      return response
    }),
    // and so on…
  ])
}

PromisePool.map()

Usage

PromisePool.map<T, U>(
  array: Array<T>,
  mapper: (item: T, index: number, array: Array<T>) => Promise<U>,
  options: { concurrency: number },
): Promise<U[]>

Example

import PromisePool from 'promisedip'

const pages = [
  'https://example.com/',
  'https://wordscape.com/',
  'https://en.wikipedia.org/',
]

async function main (): Promise<void> {
  const results: string[] = await PromisePool.map(
    pages,
    async (page) => {
      const response = await fetch(page)
      return response.text()
    },
    { concurrency: 2 },
  )
}

Troubleshooting

  • PromisePool.map(readOnlyArray, …) does not work with a readonly array
    • Use PromisePool.map([...readOnlyArray], …)
  • The lib does not seem to work with Node, or TypeScript, or anywhere except the browser
    • TL;DR: install a version >= 1.1.4
    • Explanation: I made successive mistakes in the build process, I didn't master fully exports map nor rollupjs for building UMD, CommonJS AND ESModule outputs. Now everything is fine.

Why

This package is clearly not the only one to perform promise pooling. So why "yet another …" ?

Because …

  • I wanted a dependency-free package that I could use for frontend projects
  • Since I intend to use it on frontend apps, I wanted it to be extremely lightweight: the JavaScript module build is less than 1kB
  • I wanted a pooler that I could use at different scopes, from very global to very local
  • I wanted to be able to add promises in the stack on the fly
  • I wanted a proper naming
  • I wanted proper typings
  • I wanted JavaScript modules