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

uniform-scheduler

v1.0.0

Published

Simple JS scheduler

Downloads

5

Readme

Uniform Scheduler

Latest Release pipeline status coverage report

Schedules dynamic number of similar tasks uniformly in time.

Check out an interactive demo.

Installation

Requires Node >= 20.

npm i uniform-scheduler

Usage

import { UniformScheduler } from 'uniform-scheduler';

/** Returns a promise that resolves after `duration` amount of milliseconds */
declare const sleep: (duration: number) => Promise<void>;

const scheduler = new UniformScheduler(100 /* minInterval, ms */);

const taskA = () => { console.log('task A called'); };
const taskB = () => { console.log('task B called'); };

                             /* Time(ms):                                                          */
scheduler.addTask(taskA);    /* =>   0| task A called                                              */
await sleep(225);            /*     25|                                                            */
                             /*     50|                                                            */
                             /*     75|                                                            */
                             /*    100| task A called                                              */
                             /*       |                                                            */
                             /*       |                                                            */
                             /*       |                                                            */
                             /*    200| task A called                                              */
scheduler.addTask(taskB);    /* => 225|                                                            */
await sleep(150);            /*    250| task B called                                              */
                             /*       |                                                            */
                             /*    300| task A called, minInterval = 100ms for task A is preserved */
                             /*       |                                                            */
                             /*    350| task B called, 2 tasks are now spread uniformly in time    */
scheduler.removeTask(taskA); /* => 375|                                                            */
await sleep(100);            /*    400| task A would've been called but was just removed           */
                             /*       |                                                            */
                             /*    450| task B called, minInterval for task B still preserved      */
scheduler.stop();            /* => 475| scheduler stopped, no tasks will be called anymore         */

Q&A

Q: Why is this useful?

A: One case I could think of is a web scraper that needs a low refresh latency.

Q: My tasks are drifting. The task that was supposed to run at t=250ms actually ran at t=251ms

A: The scheduler uses setTimeout under the hood. And just like setTimeout, it is a best-effort API. The scheduler only calculates the time when a task is supposed to be run and then passes it to setTimeout without doing any additional event loop magic. Consequently, +-1ms drift is common.