It is indeed impossible to achieve with process.on().

I think this is sync-prompt's own problem. There are two problems here:

1. It does not check cin.eof() after std::getline(). If checked, there would be a chance to notify the caller of this situation in some way. , giving the caller a chance to process it. In fact, not only Ctrl + C, if you press Ctrl + D to close stdin directly, you will have the same problem, and Ctrl + D is simply impossible to capture through signals.
2. sync-prompt It should not use cin directly at all, which is wrong in itself. You can try it. If you write process.stdin.on("end", function() {}) first and then execute prompt(), you will find that prompt() will return immediately. At this time, if the cin.eof() status is output in its source code, you can see that this returns true. This is because this on() call enables stream mode and closes the original stdin fd, causing the sentence getline(cin, retval) to not work at all.

If you still want to continue using it, then implement the callback mechanism mentioned in the first item above, otherwise there will be no solution at all.

Update: I just took a look at the sync-prompt warehouse and found that the author added a prompt.isEOF() function a few days ago, so I can finally make a judgment. Did you quit because of EOF? However, it seems that the latest code has not yet been released to the npm registry. If you want to use it, you need to manually download the code and compile it.

setTimeout(function(){
    console.log('Hello ' + name);
    var fruit = prompt('what is your favorite fruit? ');
    console.log('me too');
    console.log('this would be print after you type CTRL+C');
    process.exit(0);
},10);