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

batch-promises-with-delay

v1.0.6

Published

Promise batching for unreliable api calls that have rate limits

Downloads

244

Readme

Batch Promises with Delay

This module is for batching promises that need delays between batches. It also allows users to retry promises that have failed. One situation this can be useful is when dealing with unreliable api calls that have rate limits.

Installation

npm install --save batch-promises-with-delay

or

yarn add batch-promises-with-delay

Simple Usage

// simple-example.js

const batchPromisesWithDelay = require('batch-promises-with-delay')

const promises = [
  {
    func: async (a, b) => {
      /* some api call */
      /* some database save call */
    },
    args: ['A', 'B'],
  },
  {
    func: async (c, d) => {
      /* some api call */
      /* some database save call */
    },
    args: ['C', 'D'],
  },
]

const options = {
  batchSize: 3,
  delayBetweenBatches: 1000, // in ms
}

batchPromisesWithDelay(promises, options)

Options

| Property | Description | Type | Default Value | |---------------------|---------------------------------------|--------------------|---------------| | batchSize | Size of the batch | number | 1 | | delayBetweenBatches | Time delay between batches in ms | number | 1 | | retryFilters | Filters to enable retry (see below) | array of functions | [] | | greedyRetry | Retry all promises, even if they fail | boolean | false | | ignoreFailures | Quietly ignore all promise failures | boolean | false | | onSuccess | Lifecycle hook (see below) | f(args, result) | () => {} | | onFailure | Lifecycle hook (see below) | f(args, err) | null | | onRetry | Lifecycle hook (see below) | f(args) | () => {} | | onBatchStart | Lifecycle hook (see below) | f() | () => {} | | onBatchEnd | Lifecycle hook (see below) | f() | () => {} |

Retrying Promises

In certain circumstances, there will be a need to retry promises when they throw a fail condition. Such promises are thrown to the back of the queue to be retried.

The way we decide if a fail condition should be retried is by using an array of filters. As long as one filter in an array passes, the promise is retried.

const retryFilters = [
  (err) => {
    err.message == 'retry me'
  },
  (err) => {
    err.statusCode == 418
  },
]

Lifecycle hooks

These are functions that are called at certain points in the lifecycle of each batch or promise.

The following arguments are worth mention:

  • args refers to the arguments that are passed as part of the "promises". The reason this is here is partly to give context to the result, and partly to identify which promises are failing by providing some data for logging.
  • result is the result that is gotten from the promise that has been executed.
  • err is the error object.