Windows: Closing development leaves phantom processes

[FredKSchott]

Original Discussion: https://www.pika.dev/npm/snowpack/discuss/295
/cc @Ciantic, @FredKSchott

Tracked it down to readline not properly triggering execa cleanup.

@Ciantic if we can't get execa's automatic cleanup triggering, we can try to connect our own exit listener to call .kill() on the execa processes manually.

[Ciantic]

I opened an issue to here sindresorhus/execa#429 with my smaller repro.

[FredKSchott]

@Ciantic any luck? I'm going to go ahead and close this since we are no longer doing any capturing of SIGKILL commands or the like that could be causing this on our end. If there is an issue here, then it's inside of execa, and hopefully they're able to reproduce and fix.

[Ciantic]

I will try to reproduce this again. But last with tests I was able to reproduce this in Windows 10 Virtual Machine, so it did definitely exist, and it was reproducible most of the time.

I actually switched using WSL (Linux Environment) because of this, so I didn't dig any deeper.