NestJS’s multi-throttler setup has a quiet footgun. I fixed it.
When you configure multiple throttlers and decorate an endpoint with @Throttle({ sensitive: {…} }), ALL throttlers still apply. The only workaround is manually skipping each unwanted one — which silently breaks whenever a new throttler is added to your module.
So I built nestjs-selective-throttler.
A build-time script scans your modules, discovers all configured throttler names, and generates the skip logic automatically. At the endpoint level, you just declare what you want:
@SingleThrottle(‘sensitive’) → only that throttler runs. Everything else is skipped.
Zero runtime overhead. Full TypeScript support. Drop-in alongside existing setups.
Hit the same issue? Links here 👇
📦 npm: <a href="http://npmjs.com/package/nestjs-selective-throttler" target="_blank" rel="noopener nofollow">npmjs.com/package/nestjs-selective-throttler</a>
🔗 GitHub: <a href="http://github.com/orknist/nestjs-selective-throttler" target="_blank" rel="noopener nofollow">github.com/orknist/nestjs-selective-throttler</a>
Feedback and PRs are welcome!

Welcome to the NestJS Developers Hub, a collaborative community for developers passionate about NestJS! Whether you're a seasoned expert or just getting started, this group is dedicated to sharing knowledge, solving problems, and advancing our skills

Nestjs Developers

nestjs-selective-throttler is a library that fixes a footgun in NestJS's multi-throttler setup where decorating an endpoint with @Throttle still applies ALL configured throttlers. The solution uses a build-time script to scan modules, discover all throttler names, and auto-generate skip logic. The @SingleThrottle('name') decorator then ensures only the specified throttler runs, with zero runtime overhead and full TypeScript support.