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
Cancel concurrently tasks leave running processes even with --kill-others
#67
Comments
Which version of NPM are you using? Have you seen this issue https://github.com/kimmobrunfeldt/concurrently/issues/4 |
hey here is my {
"npm": "3.10.6",
"ares": "1.10.1-DEV",
"http_parser": "2.7.0",
"icu": "57.1",
"modules": "48",
"node": "6.3.0",
"openssl": "1.0.2h",
"uv": "1.9.1",
"v8": "5.0.71.52",
"zlib": "1.2.8"
} OS: I noticed this bug on Win7, Win8.1 and Win10. |
I have the same problem on Windows 10. Tried both yarn 0.18.0 and npm 3.10.9. |
I think I'm getting this, but not on when using CMD. Only when using gitbash (mingw). |
Strange.. I tried it with cmd, powershell, mingw and mingw inside powershell, but tasgmanager said, the watch task ist runnning, even after break (ctrl + c)... I need to check it again Happy new Year 🎆 |
Published v3.2.0! |
Awesome, thanks @gustavohenke! |
Sorry for my late response! Thanks! |
I'm using concurrently v3.5.1 & gitbash (MINGW) on Windows 10. After trying to cancel w/ ctrl + c, it appears to cancel, but then when I make any file changes there's still output from nodemon/react hot reload. PS, I'm new to reporting bugs, so bare with me. :) |
Also happening to me, latest version, npm 3, Win 10 |
Same here. Ctrl+c exits but the process is still ongoing. Even everything I have after |
Hey there,
when i run conccurrently and then cancel it with ctrl+c, there are running tasks.
Is there a concurrently
cleanup
or something like that?My package.json:
running those tasks with
npm
instead ofyarn
results in the same issue.The text was updated successfully, but these errors were encountered: