You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having a weird issue, which appeared only after I started using nvmw:
Whenever I use ctrl-c to stop the running script (on MINGW64 bash terminal) the NodeJS process is not killed. Using the normal windows terminal (win+r > cmd) everythin works fine.
My Environment
Windows 10
Expected Behavior
Script to stop and NodeJS process to get killed
Actual Behavior
Script stops but NodeJS process lives on
The text was updated successfully, but these errors were encountered:
I typically stick to the normal shell because I used to run into countless issues with other shells that manipulate the OS in non-standard ways. Issue #58 isn't specifically related, but it did inspire a few comments from other users regarding different shells... maybe there are some insights there.
I'm having a weird issue, which appeared only after I started using nvmw:
Whenever I use ctrl-c to stop the running script (on MINGW64 bash terminal) the NodeJS process is not killed. Using the normal windows terminal (win+r > cmd) everythin works fine.
My Environment
Expected Behavior
Script to stop and NodeJS process to get killed
Actual Behavior
Script stops but NodeJS process lives on
The text was updated successfully, but these errors were encountered: