swarthy

ES modules build is not ready yet. There are some more requirements to get this done https://www.typescriptlang.org/docs/handbook/esm-node.html

Hi. Error message is invalid, don't use cluster directly in Mutex constructor, see [redlock example](https://github.com/swarthy/redis-semaphore#redlockmutex).

There are tests for redlock semaphore https://github.com/swarthy/redis-semaphore/blob/master/test/src/RedlockSemaphore.test.ts. Case similar to yours is covered, check infrastructure (network). Or please add PR with failing test with redlock semaphore.

Hi! Sorry for confusing README example. Redlock algorythm requires independent nodes, so you need 3+ independent single nodes. Please see https://redis.io/docs/latest/develop/use/patterns/distributed-locks/#the-redlock-algorithm

@jokester Hi! Thanks for PR! Please, check review comments. > If user didn't have ioredis as explicit dependency this could break something in rare case. I guest we can mark...

Hi! The `src` folder is included in the package intentionally, because it is convenient for debugging errors occurring inside the library. Why it is necessary to remove it?

Released in v5.6.2

Hi. Because there are internal data/state in each instance such as identifier, refresh interval, "lost lock" behaviour etc. Lifecycle of `Mutex`/`Semaphore` implies that the instance will be created just before...