Signals like SIGHUP aren't propogated about scripty HOT 5 OPEN

I think we should forward any signals received upward

from scripty.

Okay. I have a local, minimal, ad hoc test case, and can at least look at a fix, but I'm not sure I have the time this week to work on a regression test.

from scripty.

This may just be a problem with npm. I remember running into precisely this issue at client with a plain (non-scripty) npm script. Though that was back in npm 1.x days. No idea if it's been resolved with npm 2 or 3.

from scripty.

@Schoonology still an issue, I presume? any chance to hack up a test case?

from scripty.

I've decided to give up using scripty due to issues with SIGNALs and wrote.sh script paths directly to package.json. Eventually reducing the number of third-party dependencies is always good.

"start:prod": "scripty" -> "start:prod": "./npm-scripts/start/prod.sh"

One more notice: don't forget to prepend your final node calls with exec in .sh script. Otherwise, SIGNALs won't be transferred from SH to Node because if a child process started in blocking mode SH can't listen to signals.

#!/bin/sh
... some condiguring code ...
exec node ./app.js

from scripty.