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

easyscheduler

v2.0.1

Published

A simple scheduler with customizable and scalable rate limits

Downloads

8

Readme

Why another rate limiter?

I was using Riot Games' API and they featured two rate limits. They allow 20 requests per second, and 100 every 2 minutes. I couldn't find a solution I deemed simple enough so I made my own.

const scheduler = new Scheduler(options: SchedulerOptions[])

scheduler.schedule(fn) => Promise<ReturnType<fn>>

Example

import Scheduler, { DURATION } from "easyscheduler"
const scheduler = new Scheduler([
	{ duration: DURATION.SECOND, call_limit: 10 },
	{ duration: 2 * DURATION.SECOND, call_limit: 15 }
])

for (let i = 1; i <= 30; i++)
	scheduler.schedule(console.log, i)
// or
for (let i = 1; i <= 30; i++)
	scheduler.schedule(() => console.log(i))

Currently, in 2.0, call order is not consistently respected. After any rate limitation hits, calls will be re-ordered to the end of the schedule.

Features

// new Scheduler(SchedulerOptions[])
const scheduler = new Scheduler([{ duration: DURATION.SECOND, call_limit: 10 }])

// scheduler.schedule(fn, ...args)
for (let i = 1; i <= 30; i++)
	scheduler.schedule(console.log, "test")
// scheduler.time_until_available()
console.log(scheduler.time_until_available()) // in milliseconds, should be around 1000 in this example

// scheduler.map(fn)
const nums = [1, 2, 3]
const promises = nums.map(scheduler.map(v => v * 10))
Promise.all(promises).then(console.log)

Riot Fetch Wrapper Example

import Scheduler, { DURATION } from "easyscheduler"
const scheduler = new Scheduler([
	{ duration: DURATION.SECOND, call_limit: 20 },
	{ duration: 2 * DURATION.MINUTE, call_limit: 100 }
])

const riot_fetch = (endpoint: string) => scheduler.schedule(fetch, endpoint, { headers: { "X-Riot-Token": "RIOT-GAMES-TOKEN" } }).then(res => res).then(res => res.json())

TODO:

  • [ ] Maintain call order after a rate limit is reached
  • [ ] Add option to maintain call_history records until Promises fully resolve when the function returns a Promise
  • [ ] Add logic to warn for using pointless rate limits (if you can make 1 call per second, there's no point in having a second rate limit that only allows 60 calls per minute)