Update express-rate-limit: 5.2.3 → 5.5.1 (minor) #107
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ express-rate-limit (5.2.3 → 5.5.1) · Repo
Commits
See the full diff on Github. The new version differs by 43 commits:
5.5.1change missing req.ip from thrown error to logged error.call out AWS API Gatewaylink to precise-memory-rate-limit5.5.0Document new options param on handlerMerge pull request #245 from takeshirs/feature/handler-options5.4.1throw if req.ip is undefinedimprovements for "decrement hits with closed response and skipFailedRequests" test5.4.0test improvements:typo fix and name clarificationdev dep bumpMerge pull request #244 from takeshirs/feature/custom-req-param-nameAdd max function exampleMerge pull request #252 from nfriedly/dependabot/npm_and_yarn/semver-regex-3.1.3Bump semver-regex from 3.1.2 to 3.1.3renamed property and added testallow handler to access optionsadd option to allow custom param name added to req5.3.0fixup publish workflowdep bumps from npm audit fixclarify success/fail skipping option descriptionsAdd optional requestWasSuccessful callback for use with skipFailedRequests and skipSuccessfulRequests options (#241)lintadded test for 'requestWasSuccessfull' option based on query parameterApply suggestions from code reviewintroduced 'requestWasSuccessful' optionEWN-17662/express-rate-limit - add skipSuccessfulCallback (#1)test on windows and mac (in addition to existing linux tests)make tests run on windowslink ci badge to gh actions page5.2.6Merge pull request #224 from Hypfer/masterChange Date.toGMTString to Date.toUTCString due to deprecationUpdate npm version badge source5.2.5dep bumpMerge pull request #222 from vpeshka/fix/bluebird-warningsFix - Warning: a promise was created in a handler but was not returned from it when used with Bluebird.Clarifying limitations of default memory storeDepfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands