-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems spawning processes in Windows #182
Comments
execa looks like a good way to go. I tried cross-spawn and it doesn't support SIGTERM, hopefully execa does. |
For reference nodejs/node#12378 |
In execa, it tries SIGTERM and if no response then falls back to SIGKILL. Seems to be the quickest win here. Drop in execa and if in the future more control is required, back it out with good test coverage.
|
@jbolda agree, let's see if we can just use execa. |
When you spawn a child process in windows,
Potentially related https://stackoverflow.com/questions/32705857/cant-kill-child-process-on-windows ?
Consider using [execa] ?
The text was updated successfully, but these errors were encountered: