Justin Chase

Also, it would be nice to see standards delivered for the file formats being persisted and some considerations for versioning. If the files are distributed and many people access the...

@ashleydavis Nightmarejs was the old name, it has been retired and replaced with just "nightmare". Notice the last published date.

I'm trying to build an app which does local indexing of files, nothing super fancy but essentially I want to be able to extract key words and phrases and build...

I'm adding the error handler to try to gather more information, I'll either just close this or update with more details if there is more context worth sharing.

In your killer module: https://github.com/gilamran/tsc-watch/blob/master/lib/killer.js#L18 Why aren't you just using the node api's `process.kill()` function? https://nodejs.org/dist/latest-v12.x/docs/api/child_process.html#child_process_subprocess_kill_signal Essentially in that function I'd like to handle the `process.on('close', ...)` and if its...

I just went in and modified the code in my node_modules to play around with it and calling `process.kill(KILL_SIGNAL)` results in the same behavior. After playing around with it I...

Well after looking at this pretty closely I think that tsc-watch is actually fine, not the one causing the "problem" for me. However, it did appear to be `tsc-watch`, so...

in the app that is running if you implement a handler for 'SIGTERM' and never call process.exit() it will basically hang. ```ts // index.js setInterval(() => console.log('still alive...'), 3000) process.on('SIGTERM',...

There has been some developments on this issue by the way, in some other repos where I also filed this bug (not knowing exactly where its originating from) it appears...

May be related to https://github.com/nodejs/node/issues/34830