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

rate-limit-concurrent

v1.0.5

Published

Rate limit your concurrent requests to resource server to ensure you don't hit 429 status code.

Downloads

5

Readme

rate-limit-concurrent

Rate limit your concurrent requests to resource server to ensure you don't hit 429 status code.

Sample typescript code to explain working

import rateLimit from 'rate-limit-concurrent';
const mockFetch = async (reqNo: number, delay: number) => {
  console.log(`${reqNo} started at ${(Date.now() - start) / 1000}s`);
  const took = `${reqNo} took: `;
  console.time(took);
  setTimeout(() => {
    console.log(`${reqNo} ended at ${(Date.now() - start) / 1000}s`);
    console.timeEnd(took);
  }, delay);
};

const start = Date.now();
const slowFetch = rateLimit(mockFetch, 1000, 3);
// odd request are slowed down, even request complete quickly to simulate real time variations in network requests
for (let i = 1; i <= 5; i++) slowFetch(i, i % 2 === 0 ? 50 : 5000);

Output of code:

1 started at 0s
2 started at 0.005s
3 started at 0.005s
// only 3 (maxConcurrent) queued
2 ended at 0.062s
2 took: : 57.416ms
// although there is one empty slot, 4th request doesn't queue for minDelay (1s)
4 started at 1.012s
// 5th request queues despite 1 & 3 not completing because we wait only minDelay not till request completes
5 started at 1.013s
4 ended at 1.074s
4 took: : 62.147ms
1 ended at 5.015s
1 took: : 5.012s
3 ended at 5.017s
3 took: : 5.013s
5 ended at 6.016s
5 took: : 5.004s

Sample js code

// es module
import rateLimit from 'rate-limit-concurrent';
// commonJS
const rateLimit = require('rate-limit-concurrent');
const mockFetch = async (reqNo, delay) => {
  console.log(`${reqNo} started at ${(Date.now() - start) / 1000}s`);
  const took = `${reqNo} took: `;
  console.time(took);
  setTimeout(() => {
    console.log(`${reqNo} ended at ${(Date.now() - start) / 1000}s`);
    console.timeEnd(took);
  }, delay);
};

const start = Date.now();
const slowFetch = rateLimit.default(mockFetch, 1000, 3);
// odd request are slowed down, even request complete quickly to simulate real time variations in network requests
for (let i = 1; i <= 5; i++) slowFetch(i, i % 2 === 0 ? 50 : 5000);