Async mutex lock for managing access to a shared resource
MIT License
Async mutex lock for managing access to a shared resource
It provides a safe and easy way to ensure that only one operation accesses a particular resource at a time, preventing race conditions and ensuring data integrity.
npm install p-mutex
import Mutex from 'p-mutex';
const mutex = new Mutex();
const sharedArray = [];
async function addToSharedArray(item) {
await mutex.withLock(async () => {
const item = await getItem();
sharedArray.push(item);
});
}
addToSharedArray('A');
addToSharedArray('B');
Mutex()
Creates a new mutex object.
.withLock(task)
Automatically manages the lock during the execution of the given task
.
It ensures that the mutex is locked before the task
executes and automatically releases the lock afterward, even if an error occurs during the execution.
Parameters:
task
: A function that performs the actions you want to execute while the lock is held. It can be async.Returns the result of the task
function.
[!TIP] Prefer using this method for most use cases as it handles the complexities of lock management and is less prone to errors. Use the lock and unlock methods directly only when you need more control over the lock management process.
.lock()
Acquires the lock.
Returns a promise that resolves when the lock has been acquired.
[!IMPORTANT] Ensure every
.lock()
is paired with.unlock()
. Use atry...finally
block for safe lock management; the finally block ensures the lock is released, even if an error occurs.
.unlock()
Releases the lock.
.isLocked
Indicates whether the mutex is currently locked.