-k option kills process but triggers error message

[finnmerlett]

I'm using concurrently to run react-native start whilst I build my release app and install it on my phone. Using the -k option causes the react-native start to exit when the build finishes, as desired, but it exits with an error code which isn't very visually nice. Is there a way to cause the react-native start process to exit as cleanly as if you had hit ctrl-c?

Many thanks, and great module!

[gustavohenke]

Not possible yet. -k is hardcoded to send SIGTERM, but I suppose it could be customised to send SIGINT instead, so

• -k SIGINT -> sends SIGINT
• -k -> sends SIGTERM

[Yuri6037]

In other words: this software should not be used as all automation scripts will miserably fail currently, nice!

[gustavohenke]

Hey @Yuri6037, if you don't like this behaviour you're welcome to propose a pull request to change it 😊

[Yuri6037]

Well I used modded a simpler tool: https://github.com/Yuri6037/parallelshell/blob/master/index.js