Adam Pflug

I haven't been able to come up with a clean solution really. My workaround so far is to just always follow up `.chain()` with either `.pluck('attributes')` or `.invoke('toJSON')`. This lets...

@AnandChowdhary I ran into some unexpected delays because of offline stuff, but I'm actively working on this now and targeting a beta release next week.

@animir I've been considering it, but I have a few reservations: 1. `rate-limiter-flexible` doesn't have a pluggable backend architecture, so it requires updates to the core to add new store...

Thanks for the offer of support @ErisDS, If you can help with updating dependencies and testing/validating those changes I'd be love to review and merge that kind pull request and...

@ErisDS Sounds good, I sent you an invite as a contributor. Let's start with the dependency updates and underscore->lodash swap for the first push. Also good catch on the license...

@ErisDS sure!

Looks like a bug resulting from a race condition when you have multiple concurrent requests. Both processes get the current counter value (e.g. 1), and then both processes attempt to...

Agreed, the trick is that makes it cache engine specific code so it would need to be fixed in each storage adapter individually... To me going to all the effort...

I should have some time to address this in early June. Note that because of the nature of the issue it'll likely require a breaking change (v2.0), which will require...

@jerroydmoore long story short, I'm currently thinking it will only affect the data stores, but that will mean you'll need to update your data stores if you want to migrate...