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

@infra-blocks/retry

v0.4.1

Published

This repository exports utilities for generic retry logic.

Downloads

849

Readme

ts-retry

Build Release Update From Template

This repository exports generic retry utilities. It leverages the promise-retry library under the hood. It extends it with an event emitter API and renames some of its configuration variables.

Retry configuration

The retry configuration uses the following values:

  • minIntervalMs. The minimum wait time between attempts. Defaults to 1000.
  • maxIntervalMs. The maximum wait time between attempts. Defaults to Infinity.
  • factor. The exponential factor to use. See LINK. Defaults to 1.
  • retries. The amount of retries made (not including the first call). Defaults to 60.
  • isRetryableError. A predicate function that determines whether an error should trigger a retry. Defaults to () => true.

You invoke it as such with the default configuration:

import {retry} from "@infra-blocks/retry";

// This promise resolves when `myFunc` resolves, or rejects with the last error returned
// by `myFunc` on that last retry.
await retry(myFunc);

To tweak its behaviors, simply pass the desired modifications as the second argument to the retry invocation:

await retry(
    myFunc,
    {
        retries: 9,
        factor: 2,
        minIntervalMs: 150,
        maxIntervalMs: 20_000,
        isRetryableError: (err) => err.name === "RetryableError"
    }
);

Event emitter API

The API also allows caller code to subscribe to attempt and retry events. attempt events are emitted on every attempt, including the first. retry events only start being emitted on the second attempt, meaning an error always occurred before a retry event.

The attempt event handler has the following call signature:

(params: {
    attempt: number; // Starts at 1.
    retryConfig: Required<RetryConfig<E>>; // This is the effective retry configuration used. 
}) => void;`

And the retry event handler has the following call signature:

(params: {
    retry: number; // Starts at 1.
    retryConfig: Required<RetryConfig<E>>;
}) => void;

Example:

await retry(startMongoDbContainer)
    .once("attempt", () => logger.info("starting MongoDB container"))
    .on("retry", ({retry}) => logger.debug(`polling MongoDB for health check, retry: ${retry}`));