ehmicky

When a parent process exits, its child processes are terminated by the OS, not by Node.js. Therefore, it is not possible to control which signal is being sent. (Note: when...

Thanks for the additional context, I see what you mean in terms of complexity from the caller's standpoint. You're also correct about the `cleanup` option. To be clear, this option...

Note that this is especially problematic when using `shell: true`. The following: ```js const subprocess = execa('sleep 200', {shell: true}); subprocess.kill(); await subprocess; ``` Is the same as: ```js const...

This solution (`pidtree`) started to be implemented in [this PR](https://github.com/sindresorhus/execa/pull/170#issuecomment-475307762). We first looked into build this into `childProcess.kill()`. But it turns out it was big enough that we thought this...

Promises are variables that can be awaited. `subprocess` is a mixin of a `Promise` and a child process. This might be off-topic, so I am going to hide those comments...

Hi @doublethinkio, Could you try adding the `windowsHide: false` option and see if this fixes your problem? Thanks!

@nickroberts I have updated my original message. The problem is actually not related to Node.js versions. Instead, this is happening when the process execute too fast. A discussion is currently...

Yes, this makes sense :+1:

Hi @ManiacDC, Thanks for reporting this. It seems that the problem is due to the `windowsHide` option. `npm` is not a binary but a shell file. For example, if you...

I hear you, especially the fact that this is difficult to change when `execa` is called from dependencies. Some additional issues and discussions about the `windowsHide` option: - In Execa:...