19.8.1 leaves dangling child processes on Windows

Current Behavior

When pressing ctrl+c on windows to kill a NX command (eg: a dev server), it leaves all of the sub-processes (node, esbuild, vite, etc) running.

Expected Behavior

When pressing ctrl+c on windows to kill a NX command (eg: a dev server), it should kill all of the processes which were created.

GitHub Repo

No response

Steps to Reproduce

Run a NX command which uses the nx:run-commands executor
Kill the command in the terminal with ctrl+c
Check Windows Task Manager to see that the process that was started is still running (this is easiest to see if the first process starts a server on a port since the second run will now fail since that port is still in-use)

Nx Report

Node           : 20.17.0
OS             : win32-x64
Native Target  : x86_64-windows
pnpm           : 9.11.0

nx                 : 19.8.1
@nx/js             : 19.8.1
@nx/jest           : 19.8.1
@nx/linter         : 19.8.1
@nx/eslint         : 19.8.1
@nx/workspace      : 19.8.1
@nx/devkit         : 19.8.1
@nx/esbuild        : 19.8.1
@nx/eslint-plugin  : 19.8.1
@nx/plugin         : 19.8.1
@nrwl/tao          : 19.8.1
@nx/vite           : 19.8.1
typescript         : 5.6.2

Failure Logs

N/A

Package Manager Version

No response

Operating System

[ ] macOS
[ ] Linux
[X] Windows
[ ] Other (Please specify)

Additional Information

This is the commit which broke it: https://github.com/nrwl/nx/pull/28073

This is the NodeJS reference for why it's broken: https://github.com/nodejs/node/issues/29837#issuecomment-538438824

nrwl / nx

19.8.1 leaves dangling child processes on Windows #28207