moxystudio/node-proper-lockfile

Issues

• macOS: Error: ENOENT: no such file or directory, lstat '/private/tmp/ ...

  #100 opened 4 years ago by unphased
  2

• Impossible to compose a lock..

  #108 opened 2 years ago by mikegwhit
  1

• Error: Lock file is already being held

  #92 opened 5 years ago by marcj
  4

• Locks taking longer than I expect

  #118 opened 9 months ago by dsellarsnr
  0

• It doesn't work in Windows, or I don't understand it's logic

  #115 opened 2 years ago by jsonslim
  1

• The lib doesn't work as expected, or I don't understand it's purpose

  #114 opened 2 years ago by jsonslim
  1

• Cannot read property 'updateTimeout' of undefined

  #113 opened 2 years ago by Rinse12
  1

• bug: Ctrl-C doesn't work if just requiring proper-lockfile

  #111 opened 2 years ago by aslushnikov
  0

• Cannot kill debug client

  #110 opened 2 years ago by wataash
  1

• Possibility to pass the lock to another process

  #107 opened 3 years ago by julien-f
  0

• Feature Request: Provide an API to react on a stale lock that is reclaimed

  #105 opened 4 years ago by albe
  2

• Race condition in `mtime-precision/probe`

  #103 opened 4 years ago by julien-f
  4

• TypeError unref of undefined when running proper-lockfile inside of react-scripts test

  #90 opened 4 years ago by mboperator
  7

• compromised lock throws error when release is called

  #81 opened 6 years ago by pimlie
  2

• Throws error if path leading to a file doesn't exist yet.

  #99 opened 5 years ago by ZeeCoder
  4

• Cannot read property 'updateTimeout' of undefined

  #98 opened 5 years ago by linonetwo
  1

• Follow up on the mtime check precision

  #79 opened 6 years ago by satazor
  1

• Electron start with an error alert relate this package.

  #87 opened 6 years ago by elantion
  5

• Difference between lock.mtime and stat.mtime precision

  #82 opened 6 years ago by pimlie
  14

• electron app seems break

  #84 opened 6 years ago by josselinchevalay
  3

• (docs) missing information about throwing errors

  #80 opened 6 years ago by pimlie
  0

• getLocks exposes internal details of locked files

  #76 opened 6 years ago by alanshaw
  2

• Can't use proper-lockfile while debugging memory leaks

  #71 opened 6 years ago by achingbrain
  5

• Should convert retries option to object?

  #75 opened 6 years ago by alanshaw
  1

• An in-range update of lint-staged is breaking the build 🚨

  #70 opened 6 years ago by greenkeeper
  4

• lockfilePath missing in interface LockOptions

  #73 opened 6 years ago by hogacz
  3

• Pass recursive option during mkdir

  #69 opened 6 years ago by dmail
  3

• use signal-exit

  #64 opened 6 years ago by hugomrdias
  2

• [Feature Request] Export a defaultOptions object

  #59 opened 6 years ago by mvastola
  2

• Specify supported Node.js versions / transpile to es5

  #57 opened 6 years ago by vgalka-sl
  1

• compare speed test etc

  #55 opened 6 years ago by ORESoftware
  1

• Please specify the supported node.js versions, or, preferably, please convert the code to run on the lower versions of node.js.

  #51 opened 7 years ago by zeodtr
  5

• An in-range update of mocha is breaking the build 🚨

  #44 opened 7 years ago by greenkeeper
  4

• An in-range update of mocha is breaking the build 🚨

  #41 opened 8 years ago by greenkeeper
  1

• An in-range update of eslint is breaking the build 🚨

  #32 opened 8 years ago by greenkeeper
  10

• An in-range update of rimraf is breaking the build 🚨

  #34 opened 8 years ago by greenkeeper
  0

• Make this work only for node > v4

  #24 opened 8 years ago by satazor
  0

• Anyway to check if a file is locked without acquiring a lock?

  #22 opened 8 years ago by timbowhite
  2

• Compromised locks

  #11 opened 9 years ago by matteocontrini
  2

• Uncaught Exception

  #5 opened 9 years ago by DGollings
  4

• Introduce synchronous signatures

  #1 opened 10 years ago by gibson042
  7

• unref lock check interval

  #3 opened 10 years ago by bmeck
  13

• lock file prior to existence

  #2 opened 10 years ago by bmeck
  4