fix(cli): ctrl+C no longer kills processes (#11434)#11518
fix(cli): ctrl+C no longer kills processes (#11434)#11518patak-cat merged 3 commits intovitejs:mainfrom
Conversation
0ce958c to
718b443
Compare
|
I don't remember what but it causes issues. I need to look at it a bit closer |
|
I guess it's because |
Co-authored-by: Arnaud Barré <[email protected]>
|
stil not working in 4.1.1 |
|
@kinfuy kinfuy |
|
Can you provide a repro? |
|
The current processing is that ctrl c directly throws process.exit (1), which is indeed consistent with the behavior of ctrl c's unexpected exit, but this prompt will make people feel sick. Maybe there is a need to find a better way |
|
Yeah I was annoyed by this extra log but with the team we decided to go in that direction so everything is supported (shortcuts, running via npm-run-all) without configuration. The only other solution would be to allow people to out-out of shortcuts bindings. But that's one more thing to document. |
Co-authored-by: Arnaud Barré <[email protected]> close vitejs#11434

Description
The binding of shortcut keys makes
Ctrl+Cunable to exit the program directly. Although the SIGTERM signal is sent upward, it cannot end when the console has an asynchronous output task. I thinkCtrl+Cshould exitprocess.exit(1)Additional context
close #11434
What is the purpose of this pull request?
Before submitting the PR, please make sure you do the following
fixes #123).