fix(command-dev): ensure no orphaned child process on Windows #3278
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
- Summary
Fixes #3251.
On Windows, the
dev
command does not properly terminate the framework process on exit, and leaves them running even thoughnetlify-cli
has exited.This is because
execa
defaults towindowsHide: true
, which seems to interfere with terminating child processes: sindresorhus/execa#433.Other projects have also encountered this issue with execa's defaults and Windows: FredKSchott/snowpack#1022, lerna/lerna#2946.
Let's set
windowsHide: false
so that the framework process will terminate properly on exit.- Test plan
Run
netlify dev
with this PR and attempt to exit on Windows (e.g. via Ctrl-C). No framework processes should be left running after exit.- A picture of a cute animal (not mandatory but encouraged)
🦓