Roman

@rahil-p Hey, this is great! However, we can't create other class for this case. This will be confusing for everyone except you and me. Support for `node-redis` v4 package must...

@rahil-p I believe, RateLimiterRedis can be improved for `redis` v4+ with additional 5-6 if/else conditions. Is it possible to check if it is `redis` package and version is 4+ ?...

@rahil-p If there is no way to get `node-redis` client version, [storeType](https://github.com/animir/node-rate-limiter-flexible/wiki/Options#storetype) limiter option can be used to set it. It could be set to `redis4+` and then checked in...

@marlonelima Nothing the for the last month. If you wish to help, you can look at these changes and implement redis package v4+ support. Let us know.

Something wrong with Packagist repo: ``` The "http://packagist.org/p/provider-2014-10$ed15097a7afa5a3f48b27f0ce38c5e 3e8943514a0bdfd1898af31c9f8f913edb.json" file could not be downloaded: fail ed to open stream: HTTP request failed! ```

New `failed_attempt` event would be really useful. Note, for those who struggle with making a difference between `failed` job and `failed_attempts` there is job attribute `finishedOn` Unix Timestamp, which is...

@rwieruch Hi, I am not GraphQL expert, but I do have an idea. I'd do next check on the backend before getting `me` object: ```javascript let me = {}; if...

@arslnb I think, nobody looked into it.

@kpruden @thinkhy @jhurliman If you still looking for solution, [rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) package supports FIFO queue rate limiter. There is also [migration guide](https://github.com/animir/node-rate-limiter-flexible/wiki/RateLimiterQueue#migration-from-limiter), if you wish to migrate from `limiter`.

@manzan46 Hi, a-r-d tested it and found an error a couple of months ago. There were no changes since then. Also, new code requires new tests to be written. Unfortunately,...