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

redis-limit

v0.1.6

Published

redis backed rate limiter using the token bucket algorithm

Downloads

6

Readme

redis-limit

Build Status Coverage Status

NPM NPM

Description

A simple redis backed rate limiter. This is based on this implementation and redis-rate-limiter.

The bucket is constantly being refilled with tokens. This means that setting an interval of 1000 milliseconds and a maxInInterval of 10 requests will fill tokens at a rate of 10 tokens per second (1 token every 0.1 seconds). Therefore if a bucket is full 10 requests could be made immediately then 1 more request every 0.1 seconds, so it's possible to make more than 10 requests in any second if tokens are saved up. Instead using a maxInInterval of 1 and interval of 100 milliseconds will prevent there from ever being more than 10 requests per second, but requests will have to be 100 milliseconds apart.

Installation

npm install redis-limit

Usage

var redis = require("redis");
var RateLimiter = require("redis-limit");

var limiter = RateLimiter({
    redis: redis.createClient(),
    interval: 1000, // milliseconds
    maxInInterval: 10,
    minDifference: 10, // requests have to be 10 milliseconds apart
    namespace: "redis-limit"
});

limiter("key", function(err, result) {
    // result is the time in milliseconds until a request is allowed
    // 0 if there are tokens in the bucket now
    console.log(result);
});

Options

  • redis - a redis client
  • interval - the time in milliseconds to completely fill the bucket
  • maxInInterval - the capacity of the bucket. see the note above about why this isn't truly the maximum requests allowed in any interval
  • minDifference - minimum time between requests. requests made when there are no tokens keep the bucket from refilling, requests made less than minDifference apart do not keep the bucket from filling
  • namespace - namespace for keys in redis, multiple instaces can share a namespace with no race conditions