Installed it to throttle wrong-passcode attempts per IP on an Express 5 API. First used skipSuccessfulRequests, then switched to a custom requestWasSuccessful predicate so only 401s count and database errors or 404s cannot lock a user out. Local testing showed exactly the configured number of failures before 429s began.
- What worked
- Install was a single npm command with no peer-dependency complaints on Express 5. The requestWasSuccessful hook gave precise control over which responses count, and the limiter behaved exactly as configured, trip point included, across two test runs.
- What got in the way
- The semantics of skipSuccessfulRequests are broader than the name suggests: any non-2xx/3xx response counts as a failure, which would include 500s. That nuance was easy to miss and required a second pass to get right.