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 🙏

© 2026 – Pkg Stats / Ryan Hefner

precurring

v1.0.6

Published

A tiny 280 byte library for recurring Promises

Downloads

17

Readme

precurring - Recurring Promises

npm build status

Installation

npm install --save precurring

Alternatively, the UMD build is available on unpkg:

<script src="https://unpkg.com/precurring/dist/precurring.umd.js"></script>

You can find the library on window.precurring.

Examples

Pinging a server

import precurring from 'precurring';

const ping = precurring({
  fn: () => fetch('/ping'),
  interval: 5000, // fetch every 5 sec
  timeout: 20000, // wait 20 sec max (optional)
  onSuccess: console.log,
  onError: console.error,
});

ping.start();

Stopping after X errors

import precurring from 'precurring';

let counter = 0;

const instance = precurring({
  fn: myFunction,
  interval: 1000,
  onSuccess: console.log,
  onError: () => {
    if (++counter === 3) {
      instance.stop();
    }
  },
});

instance.start();

Docs

precurring

Takes an Object with all the properties listed below and returns an Object with start and stop methods.

  • start() starts the interval of calling fn repeatedly.
  • stop() stops it accordingly.

fn ((...args: any[]) => Promise<any>)

A function returning a Promise. This is a wrapper function over your own logic, which you want to repeatedly call. The value it resolves to is passed to onSuccess. If it rejects, the error is passed to onError.

interval (number)

A number in milliseconds between calls of fn. To be more precise, it is the time between the previous Promise settling, and fn being called again. Due to the library using setTimeout, this specified number is not 100% reliable, see accuracy.

timeout (number - optional)

A number in milliseconds after which to cancel fn. Note that this does not actually stop the execution of fn but instead ignores its return value after it times out. The timeout value is also subject to the accuracy issues. Since this value is optional, the default behavior is to wait however long it takes for the Promise returned by fn to settle.

onSuccess ((val: any) => any)

A callback function which is called with the value that fn's Promise settles with.

onError ((error: any) => any)

A callback function which is called with whatever fn's Promise rejects with.

Accuracy

Under the hood, setTimeout is used throughout this library. Because of how it is implemented, it does not guarantee the execution time of its callback function. Take this explainer from the MDN docs:

Note: The specified amount of time (or the delay) is not the guaranteed time to execution, but rather the minimum time to execution. The callbacks you pass to these functions cannot run until the stack on the main thread is empty.

As a consequence, code like setTimeout(fn, 0) will execute as soon as the stack is empty, not immediately. [...]

However, in most cases this is negligible. If you rely on a more accurate implementation, you should look for a different implementation/library.

References

License

MIT © Lion Ralfs