Closed sramam closed 2 years ago
Not sure I understand why this happens, but adding a noop signal handler for SIGUSR2 allows a successful restart.
process.on("SIGUSR2", () => {});
The best I can make out from the documentation - this is an optional signal. Concurrently doesn't seem to require it. Would appreciate being enlightened.
Hopefully the workaround (is it?!) will help others.
Use case
I need to run an aux process and
micro-dev my-server.js
. I use concurrently for this.The problem
Changes are detected and a restart attempt it made. However, the restart process never actually executes.
I've narrowed it down to the SIGUSR2 event emission - meaning
micro-dev
works as expected until it tries to emit that event. And removing that event emission, restart works as expected.Wondering why it's needed and what good options are available to resolve my issue