Edit: it may have been a different watchman, but same point still applies.
It’s been a few years, so perhaps it got addressed, but this library used to introduce a “memory leak” by design, by infinity storing pointers to files being watched.
Ultimately I ended up fixing it by writing my own version using native system calls available on Node.
The moral of the story, this library is great if you are building cross platform dev tool. It is not (at least wasn’t at the time) great for long lived processes that target only one type of operating system.
It’s been a few years, so perhaps it got addressed, but this library used to introduce a “memory leak” by design, by infinity storing pointers to files being watched.
It was a pain to isolate (https://techtldr.com/simple-guide-to-finding-a-javascript-me...)
Ultimately I ended up fixing it by writing my own version using native system calls available on Node.
The moral of the story, this library is great if you are building cross platform dev tool. It is not (at least wasn’t at the time) great for long lived processes that target only one type of operating system.