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 🙏

© 2026 – Pkg Stats / Ryan Hefner

nestjs-graphql-rate-limit

v1.0.1

Published

Rate Limit module with Redis storage support for NestJS GraphQL APIs

Downloads

32

Readme

NestJS GraphQL Rate Limit

A Rate Limit implementation for GraphQL APIs using NestJS

Installation

npm install nestjs-graphql-rate-limit

How to use it?

  • After installing the package, make sure you have Redis installed and running. See Redis Docker Image
  • Set STORE_HOST STORE_PORT STORE_THROTTLE_DB environment variables in your Nest project.

Example:

#Depending on where you run and which hostname you set, set your hostname.
#If you run it locally you can set it to "localhost" or if you run it on Docker, you can set whatever hostname you gave.
STORE_HOST=redis
STORE_PORT=6379
#DB option is up to you between 0-15.
STORE_THROTTLE_DB=2
  • Make sure you are returning the execution context.
GraphQLModule.forRoot({
  context: ({ req, res }) => ({ req, res }),
})
  • Import GqlRateLimitModule module into your Nest project. (Assuming you will throttle your Query & Mutations globally, importing into AppModule is highly recommended for availability reasons)

Example:

// app.module.ts
import { Module } from '@nestjs/common';
import { GraphQLModule } from '@nestjs/graphql';
import { AppResolver } from 'src/app.resolver';
import { GraphQLError } from 'graphql';
import { GqlRateLimitModule } from 'nestjs-graphql-rate-limit';

@Module({
  imports: [
    GqlRateLimitModule,
    GraphQLModule.forRoot({
      autoSchemaFile: true,
      context: ({ req, res }) => ({ req, res }),
      formatError: (error: GraphQLError) => {
        return {
          message: error.message,
          status: error.extensions.exception.status,
        };
      },
    }),
  ],
  providers: [AppResolver],
})
export class AppModule {}

Usage

// app.resolver.ts
import { Query, Resolver } from '@nestjs/graphql';
import { RateLimit } from 'nesjs-graphql-rate-limit';

@Resolver()
export class AppResolver {
  @Query(() => String)
  @RateLimit(2, 10)
  async someQuery(): Promise<string> {
    return 'Hello from throttled query';
  }
}

Documentation

  • RateLimit

Takes limit ttl arguments in given order.

Argument | Type | Description --- | ---- | ------- limit | number| Amount of requests client can make in given TTL ttl | number| Time-to-live in seconds

Notes:

@RateLimit(2, 10) means, client can only make 2 requests in 10 seconds.

Expected behaviour:

After exceeding the limit of 2 requests, server will respond with X-Retry-After header and rate limit will reset after 10 seconds starting from the last second request.