Signals like SIGHUP aren't propogated #44

Activity

1. searls commented on Oct 12, 2016

   

   searls

   on Oct 12, 2016

   Member

   More actions

   I think we should forward any signals received upward
2. Schoonology commented on Oct 12, 2016

   

   Schoonology

   on Oct 12, 2016

   ContributorAuthor

   More actions

   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.
3. jasonkarns commented on Oct 12, 2016

   

   jasonkarns

   on Oct 12, 2016

   Last edited by jasonkarns

   Member

   More actions

   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.
4. jasonkarns commented on Dec 18, 2018

   

   jasonkarns

   on Dec 18, 2018

   Member

   More actions

   @Schoonology still an issue, I presume? any chance to hack up a test case?
5. korniychuk commented on Sep 26, 2021

   

   korniychuk

   on Sep 26, 2021

   Last edited by korniychuk

   More actions

   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