node-proper-lockfile icon indicating copy to clipboard operation
node-proper-lockfile copied to clipboard

An inter-process and inter-machine lockfile utility that works on a local or network file system.

Results 19 node-proper-lockfile issues
Sort by recently updated
recently updated
newest added

when attempting to compose a release function, e.g. so that re-requesting the lock (if it exists) returns the release function, it fails stating: `TypeError: method is not a function` Example...

I'm using proper-lockfile in a Jest test suite which is executed in parallel across multiple processes. My code ``` import * as lockFile from 'proper-lockfile'; import {readJsonSync, writeJSONSync} from "fs-extra";...

My use case: I want to acquire a lock on a directory and, if successful, run a new process which will do some work in this directory and release the...

Closes #105 TODO: - [ ] Add tests - [ ] Add docs

The use case is a storage system (database) that uses a stale lockfile to detect crashes and then execute data recovery procedures (see https://github.com/albe/node-event-storage/issues/165). Right now, it's not possible to...

See #103 Quick and untested implementation.

Two parallel calls, `cachedPrecision` is not defined in both, both will call `utimes` then `stat`, and `Object.defineProperty` will be called twice. This does not throw `TypeError: Cannot redefine property` because...

Ref: #81 Strict mode is currently only used for toggling compromised lock behaviour

Based on the readme: > realpath: Resolve symlinks using realpath, defaults to true (note that if true, the file must exist previously) This explains that the setting is true by...

Is it intended behaviour that calling `release` for a lock which has been compromised throws an error? It feels counter-intuitive to me. Maybe we could add a `strict` mode, which...