Releases: adiologydev/oak-rate-limit
Releases · adiologydev/oak-rate-limit
0.1.1
Summary
- Updated
Oakto v11.1.0 - Updated
redisto v0.26.0 - Updated usage implementation. You require to put an
awaitin yourapp.use(). i.e.app.use(await RateLimiter())
Since the rate limiter seems to be working well, it's no longer an RC. Please report an issues on GitHub and feel free to contribute.
What's Changed
- adding redis store by @NewtTheWolf in #2
New Contributors
- @NewtTheWolf made their first contribution in #2
Full Changelog: 0.1.0-rc2...v0.1.1
0.1.0-rc2: onRateLimit and skip
Two new options to provide customizability for users in 0.1.0-rc2.
- onRateLimit: You can now implement a custom method to handle if a client has reached the rate limit.
- skip: Ability to implement a method that will return a boolean to skip ratelimits.
0.1.0-rc1
First release candidate for oak-rate-limit.
Features
- Support for multiple cache stores*
- Custom window duration, max requests, status code, and error message support.
- Unlike traditional implementations, this uses comparisons of timestamps instead of intervals which utilize more clock cycles even if no request has been made in a while.
* Currently only contains a Map-based local store by default, feel free to make a different one if you'd like things like Redis, Memcache, etc. before it's officially released.
This version may have bugs, please create a new issue to report such issues.