Releases: express-rate-limit/express-rate-limit
Releases · express-rate-limit/express-rate-limit
v6.7.0
No functional changes.
Changed
- Updated links to point to the new
express-rate-limit
organization on GitHub. - Added advertisement to
readme.md
for project sponsor Zuplo. - Updated to
typescript
version 5 and bumped other dependencies. - Dropped
node
12, and addednode
19 to the list of versions the CI jobs run on.
You can view the changelog here.
v6.6.0
v6.5.2
v6.5.1
v6.4.0
v6.3.0
Changed
- Changes the build target to
es2019
so that ESBuild outputs code that can run with Node 12. - Changes the minimum required Node version to 12.9.0.
v6.2.1
Fixed
- Use the default value for an option when
undefined
is passed to the rate
limiter.
v6.2.0
Added
- Export the
MemoryStore
, so it can now be imported as a named import
(import { MemoryStore } from 'express-rate-limit'
).
Fixed
- Deprecate the
onLimitReached
option (this was supposed to be deprecated in
v6.0.0 itself); developers should use a custom handler function that checks if
the rate limit has been exceeded instead.
v6.1.0
Added
- Added a named export
rateLimit
in case the default import does not work.
Fixed
- Added a named export
default
, so Typescript CommonJS developers can default-import the library (import rateLimit from 'express-rate-limit'
).
v6.0.5
Fixed
- Use named imports for ExpressJS types so users do not need to enable the
esModuleInterop
flag in their Typescript compiler configuration.