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

porch

v2.0.1

Published

Promise Orchestrator: Process promise-based tasks in series and parallel, controlling concurrency and throttling

Downloads

331

Readme

Porch

Process promise-based tasks in series and parallel, controlling concurrency and throttling.

Node.js CI Coverage Status

Installation

npm install porch

Usage / API

Promise porch(tasks, concurrency, interval, failFast)

Arguments

  • tasks (Array): An array of tasks, where each task is a function that expects no arguments and will return a Promise.
  • concurrency (Number): Default: 1. Maximum number of tasks to run concurrently (in parallel).
  • interval (Number): Default: 0. Interval between each batch of concurrent tasks.
  • failFast (Boolean): Default: true. Whether to bail out when one of the promises fails. If set to false errors will be included in the results passed to then() instead of being passed independently via the catch() method.

Return value

A Promise that will resolve to an array with the results for each task. Results will be in the same order as in the input tasks array.

Examples

Series

Process each task after the other, sequentially. Each task will wait for the previous one to complete. Concurrency set to 1 (one task at a time).

import porch from 'porch';

const tasks = users.map(user => () => auth.deleteUser(user.localId);

porch(tasks)
  .then(console.log)
  .catch(console.error);
Batches

Process tasks in batches based on a given concurrency. In this example tasks will be processed in batches of 5 tasks each. Each batch waits for the previous one to complete and then performs its tasks in parallel.

porch(tasks, 5)
  .then(console.log)
  .catch(console.error);
Throttled

Same as example above but adding a 1000ms delay between batches.

porch(tasks, 5, 1000)
  .then(console.log)
  .catch(console.error);
failFast=false (don't bail out on errors)

Same as above, but in this case if a promise fails, processing will continue instead of stopping the whole thing. When failFast is set to false, errors will appear as the value/result for the relevant element in the results array (failed tasks/promises won't end up in the catch() method).

porch(tasks, 5, 1000, false)
  .then(console.log)

stream.Readable createStream(tasks, concurrency, interval, failFast)

Arguments

Same as porch().

Return value

A readable stream (stream.Readable) instead of a Promise. Each result will be emitted as a data event and the stream will operate in objectMode.

Examples

Handling each event independently... (old school)
import { createStrean } from 'porch';

createStream(tasks, 5, 1000, false)
  .on('error', err => console.error('error', err))
  .on('data', data => console.log('data', data))
  .on('end', _ => console.log('ended!'));
Piping to a writable stream
// This example assumes that tasks will resolve to string values so that the
// resulting stream can be directly piped to stdout.
createStream(tasks, 5, 1000, false).pipe(process.stdout);