Félix Saparelli
Félix Saparelli
Just to make it clear: "crashing" is an application concern; processes merely exit with a code. So what is needed is flag to exit watchexec if the child process exits...
Possibly related to #101
This is now technically possible but not yet implemented in the CLI.
That sounds reasonable
Actually I can't reproduce this. Sending SIGTERM to watchexec kills it (and the child). Can you provide more detail as to how and what you're running?
(Sorry for taking so long, I am looking at this and haven't forgotten.)
Tried fixing this for a few days but ran into issues and it's delaying release, so I'm shelving this for now. Not happy about it, but I have to get...
Haven't done anything more since. Workaround is obviously to not run as PID 1 (not hard, just wrap it in a shell), but I haven't looked deeper at how the...
Dropping a note for future visitors that for the specific case of Docker, running with [the `--init` flag](https://docs.docker.com/engine/reference/run/#specify-an-init-process) solves this without needing your own init/shell/wrapper. It would still be nice...
Not directly at the moment, but you can write a wrapper script that "filters" on the presence of `WATCHEXEC_CREATED_PATH`, for example