Stuck on an issue?

Just thought I’d provide some context on the things I hoping to accomplish for a version 2 of express-brute, which I’d like to get out for beta in June:

Major Changes

• New storage adapter layer
  • Should allow for atomic updates to storage to resolve #46
  • Ideally should generalize the storage adapter layer so that it can be used by other projects as well (not tied directly to express-brute).
  • This will unfortunately require the existing express-brute storage adapters to be updated or replaced, I’m still on the fence on whether it makes sense to create a small “migration” adapter that allows existing storage adapters to be used (without fixing the vulnerability described in #46 fixed) until suitable replacements/updates can be developed. May be better to protect people from themselves there.
• Separate out the core code from the code that interacts with express.
  • This enables me to develop a koa version as well (which would be nice because I rarely use express for new projects at this point)
  • This should also let people use the underlying rate-limiting functionality in more customized ways if they need to (#28, #22)

Minor Improvements

• Optimize hash calculation and allow it to be bypassed/overwritten (#70)
• Add the option to attach the number of remaining requests to the request object (#73)
• Look at standardizing the options between the constructor and getMiddleware() (#64, #20)