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

@withjoy/limiter

v0.1.7

Published

Api Rate limiter

Downloads

110

Readme

limiter

A wrapper for limitd-redis.

Why ?

Provides utilities and rollback functionality for our clients.

This module was originally built to work with limitd. The prior solution -- and most of the documentation surrounding our standard rate-limiting Buckets -- can be found in joylife/limitd. That solution is now deprecated.

Buckets

Each client must define the set of rate-limit Buckets that intends to use.

The set of defaultBuckets defines the standard set of ones that we've historically determined that we need. This list may be old, but that's the general idea. Your client can use any subset of these Buckets, but when it does, the Best Practice is to use the exact definition(s) here.

However, for flexibility reasons, this is not strictly enforced.

Why limitd-redis ?

Although this package is available on npm, it's no longer actively maintained. We've observed bugs in the existing published version, but these issues have already been resolved in the limitd-redis gitHub repository. To address this, we've imported the latest stable version(v7.8.1) from there github repository and using it locally in the limiter.

In case we need to update in the future, we can replace the "limitd-redis" directory with the latest version of limitd-redis from their GitHub repository.

Note: We need to add dependency from limitd-redis to limiter package json before publish. We are using limitd-redis as directly not package inside limiter.

Testing:

npm run test will run offline tests using a mock. npm run sanity-check will run against a limitd service configured to run with the test buckets.

Quick Test

node tests/performTestWithTestPerMinute.js