Aditya Mathur

Yes, that would be a dependency 🫤. Or we can use the hooks in `create-hono` to replace `$npm_execpath` with the package manager they chose for installing depns.

`MY_RATE_LIMITER` is just a variable name so you will be changing it, and the example I have got here was inspired by https://github.com/elithrar/workers-hono-rate-limit?tab=readme-ov-file#usage. So, do we need this change?

- [ ] Correct implementation of `WorkerKVStore` - [ ] Update the docs of usage

For some reason the expiration is not working correctly, here is the code - ```ts this.windowMs = 60_000 // 1 minute async increment(key: string): Promise { const keyWithPrefix = this.prefixKey(key);...

I did some digging and found that in some cases `WorkerKV` doesn't work as expected, especially if the window is small. The `expiration` or `expirationTtl` has to be greater than...

I will release a patch version, so that at least if someone wanna use `WorkerKV` it will work. And in the next minor release, I will add support for `DurableObjects`...

I deployed a new version of `@hono-rate-limiter/[email protected]`, and it seems to be working on my end. Can you also check and let me know, if it's working for you? I...

`@hono-rate-limiter/[email protected]` supports Durable Object, kindly have a look and let me know if there is any issue. https://github.com/rhinobase/hono-rate-limiter/blob/main/packages/cloudflare/README.md

If you’ve tried using it with Durable Objects, I'd love to hear your feedback, any issues you encountered, or suggestions for improvement.

Hey! were you able to solve this?