chore(deps): update dependency express-rate-limit to v7 #413
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.
This PR contains the following updates:
^6.11.2
->^7.0.2
Release Notes
express-rate-limit/express-rate-limit (express-rate-limit)
v7.0.2
Compare Source
Added
cluster-memory-store
to the readme and made a couple of other minorclarifications.
v7.0.1
Compare Source
Added
rate-limit-postgresql
to thestores
list in the readme.v7.0.0
Compare Source
Breaking
max
is set to 0:max: 0
was treated as a 'disable' flag and would allow allrequests through.
skip
function instead.
req.rateLimit.current
toreq.rateLimit.used
.current
is now a hidden getter that will return theused
value, but itwill not appear when iterating over the keys or calling
JSON.stringify()
.express-rate-limit
now targetses2022
in TypeScript/ESBuild.dts-bundle-generator
from v7 to v8.Deprecated
draft_polli_ratelimit_headers
option (it was deprecated in v6).standardHeaders: 'draft-6'
instead.onLimitReached
option (it was deprecated in v6).is an example of how to replicate it's behavior with a custom
handler
option.
Changed
MemoryStore
now uses precise, per-user reset times rather than a globalwindow that resets all users at once.
limit
configuration option is now prefered tomax
.max
is still supported. The changewas made to better align with terminology used in the IETF standard drafts.
Added
validate
config option can now be an object with keys to enable ordisable specific validation checks. For more information, see
this.
Configuration
📅 Schedule: Branch creation - "before 12pm on Sunday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.