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
Description: With concurrently -r -k npm:parcel:dev npm:serve I can't exit with any kind of input, but the same without -r works fine with e.g. Ctrl+C.
Expected Behavior: I wouldn't expect the --raw argument, which ostensibly just affects printing, to affect what my inputs are able to do.
Environment: concurrently 8.0.1 on Windows 10. reproduced with powershell and cmd.exe, also in windows terminal and VS Code's integrated terminal.
Reproduction: Try the command above, where parcel is any parcel command and serve is e.g. nodemon
Thanks!
The text was updated successfully, but these errors were encountered:
I can't reproduce it on macOS, but I did notice that parcel is possibly intercepting stdin.
As in, it has a ~1s delay before accepting the Ctrl+C, whereas nodemon (or whatever other command) by itself accepts the Ctrl+C immediately.
@paescuj do you still have a Windows VM handy to test this?
the --raw argument, which ostensibly just affects printing, to affect what my inputs are able to do.
--raw passes stdio: 'inherit' to spawned commands, therefore this issue happening isn't so surprising actually.
I know it's outside of the JS ecosystem but I had the same problem when running Java gradle build. It seems it's the only process in the list that holds it up too.
concurrently -r -k npm:parcel:dev npm:serve
I can't exit with any kind of input, but the same without-r
works fine with e.g. Ctrl+C.--raw
argument, which ostensibly just affects printing, to affect what my inputs are able to do.Thanks!
The text was updated successfully, but these errors were encountered: