async-mutex - npm Package Versions

0.5.0 - 2024/03/11

• Support priority queueing for mutexes and semaphores. A huge "thank you" goes to @dmurvihill who added this feature.
• Update dependencies.

0.4.1 - 2024/01/17

• Expand documentation and fix a few errors.
• Clear timeout after acquiring a lock in withTimeout.
• Thanks to AkatQuas and aryzing for their contributions.
• Update dependencies.

0.4.0 - 2022/09/02

This is a full rewrite of the core implementation.

• Allow negative values for semaphores.
• Allow weights for semaphore.acquire and semaphore.runExclusive. A waiter will be dispatched once the value of the semaphore is greater or equal to its weight.
• Add semaphore.getValue and semaphore.setValue.
• Allow weights for semaphore.waitForUnlock. The promise will only resolve once the value of the semaphore is greater or equal to its weight.
• Only resolve waitForUnlock once no waiters remain (fixes #52).
• waitForUnlock times out if the withTimeout decorator is used.

0.3.2 - 2021/08/30

• Add waitForUnlock for waiting until a mutex/semaphore is free for locking, thanks to Jason Gore.

0.3.1 - 2021/02/22

• withTimeout: make Jest happy and cancel timer when the mutex is acquired. Thanks to cantoine for the PR.

0.3.0 - 2021/02/05

• Deprecate Mutex::release / Semaphore::release and remove them from the documentation. The methods are still available in 0.3.x, but will be removed in 0.4.0.

  I don't like breaking existing APIs, but using those methods is inherently dangerous as they can accidentally release locks acquired in a completely different place. Furthermore, they are mostly useless for semaphores. I consider adding them an unfortunate mistake on my end.

  A safe alternative is the usage of runExclusive which allows to execute blocks exclusively and automatically manages acquiring and releasing the mutex or semaphore.

• Add Mutex::cancel / Semaphore::cancel for rejecting all currently pending locks.

• Add tryAcquire decorator for lock-or-fail semantics.

0.2.6 - 2020/11/28

• Fix a nasty bug related to consecutive calls to Mutex::release.

0.2.5 - 2020/11/28

• Nothing new thanks to NPM. Go away. Install 0.2.6.

0.2.4 - 2020/07/09

• Calling Semaphore::release on a semaphore with concurrency > 1 will not work as expected; throw an exception in this case
• Make the warning on using Semaphore::release and Mutex::release more prominent

0.2.3 - 2020/06/18

• Add alternate Semaphore::release and Mutex::release API
• Work around build warnings with react native (and probably other bundlers)