[Snyk] Upgrade rate-limiter-flexible from 2.4.2 to 8.0.1 #36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade rate-limiter-flexible from 2.4.2 to 8.0.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 29 versions ahead of your current version.
The recommended version was released a month ago.
Release notes
Package name: rate-limiter-flexible
-
8.0.1 - 2025-09-25
-
-
-
8.0.0 - 2025-09-25
-
7.4.0 - 2025-09-24
-
-
-
-
-
-
7.3.2 - 2025-09-20
-
7.3.1 - 2025-09-13
-
-
-
-
-
7.3.0 - 2025-09-05
-
7.2.0 - 2025-07-27
-
7.1.1 - 2025-05-18
- RateLimiterRedis limiter checks if points value is an integer and throws a clear error otherwise. This helps to avoid mysterious errors provided by Lua script when consuming a floating-point number of points, e.g.
-
7.1.0 - 2025-04-28
-
7.0.0 - 2025-04-05
- feat: add
- [BREAKING CHANGE] Node.js 18 support removed.
- @ avifenesh made their first contribution. Congrats!
-
6.2.1 - 2025-03-23
-
6.2.0 - 2025-03-20
-
6.1.0 - 2025-03-13
-
6.0.0 - 2025-03-12
-
5.0.5 - 2025-01-15
-
5.0.4 - 2024-10-20
-
5.0.3 - 2024-04-28
-
5.0.2 - 2024-04-25
-
5.0.1 - 2024-04-24
-
5.0.0 - 2024-02-15
-
4.0.1 - 2024-01-26
-
4.0.0 - 2023-12-16
-
3.0.6 - 2023-12-08
-
3.0.5 - 2023-12-08
-
3.0.4 - 2023-11-10
-
3.0.3 - 2023-10-30
-
3.0.2 - 2023-10-20
-
3.0.1 - 2023-10-16
-
3.0.0 - 2023-08-29
-
2.4.2 - 2023-07-27
from rate-limiter-flexible GitHub release notesv8.0.0 [BREAKING CHANGES]
RateLimiterQueueErrorimport was changed in TypeScript projects.It should be imported from defaults now.
TS definition for RateLimiterQueueError was moved to types.d.ts.
v8.0.1:
index.d.tsfile was moved outside of lib directory and renamed totypes.d.ts.Thanks @ wildfluss and @ PaulAnnekov for help.
💿
V8 fix TS definition
In version
7.2.0RateLimiterDrizzlelimiter was added. Read about it on wikiThanks @ Nayanchandrakar !
In version
7.3.0disableIndexesCreation option added toRateLimiterMongo.In version
7.3.1conditional require of drizzle-orm was replaced with dynamic import to avoid issues with linters and tree-shakers.In version
7.3.2drizzle-orm lazy import is hidden behind function call and string concatenation to avoid unnecessary tree-shaking and statistical analysis in different bundlers.In version
7.4.0RateLimiterDrizzleNonAtomic was added. It doesn't guarantee precise events count under race conditions, but much faster than atomic limiter.💫
325 fix Vite drizzle error
#323 drizzle dynamic import
7.3.1
#323 do not depend on module type
#323 mocha include nested paths
7.3.0
7.2.0
2.1.Thank you @ roggervalf
🌞
RateLimiterEtcdandRateLimiterEtcdNonAtomicwere added. Read more on Wiki https://github.com/animir/node-rate-limiter-flexible/wiki/Etcd.This is the first time we add atomic and non-atomic limiters for the same storage. Atomic increments are necessary to count sensitive things like incorrect password or PIN tries while non-atomic increments may be better (because they are faster) when exact count doesn't matter, e.g. to protect a service against DDoS attack.
Thank you @ Tobias4872
🍇
What's Changed
RateLimiterValkeyGlideto support Valkey Glide @ avifenesh in #302 Thank you!X-RateLimit-Resetheader example was fixed. It should beMath.ceil((Date.now() + rateLimiterRes.msBeforeNext) / 1000). Thanks to @ Fdavidtr.New Contributors
Full Changelog: v6.2.1...v7.0.0
🐆
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: