EPIPE thrown when calling process.stdin.end() in node 10.15.3 on Windows

[barakman]

System:

• Version: v10.15.3
• Platform: Windows 10 64-bit

Code:

process.stdout.write("Enter input: ");
process.stdin.on("data", function(data) {
    process.stdin.end();
});

Error:

events.js:174
      throw er; // Unhandled 'error' event
      ^

Error: shutdown EPIPE
    at ReadStream.Socket._final (net.js:361:25)
    at callFinal (_stream_writable.js:612:10)
    at process._tickCallback (internal/process/next_tick.js:63:19)
Emitted 'error' event at:
    at emitErrorNT (internal/streams/destroy.js:82:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)

Notes:

• Was fine on v8.11.2 (before upgrading to v10.15.3)
• Looks similar to ENOTCONN thrown when calling process.stdin.end() in node 10.1.0 #22814

---

Alternative solution 1 (as suggested in the issue linked above):

process.stdout.write("Enter input: ");
process.stdin.on("data", function(data) {
    process.stdin.destroy();
});

Alternative solution 2 (my preferred method):

process.stdout.write("Enter input: ");
process.stdin.resume();
process.stdin.once("data", function(data) {
    process.stdin.pause();
});

Alternative solution 3 (handle the 'error' event):

process.stdout.write("Enter input: ");
process.stdin.on("data", function(data) {
    process.stdin.end();
}).on("error", function(error) {
    console.log(error.message); // shutdown EPIPE
});

[bzoz]

Can reproduce. Simply calling node -e process.stdin.end() produces EPIPE.

/cc @nodejs/platform-windows

[sam-github]

But not on linux, so I labelled as Windows

[HarshithaKP]

@barakman, Is it still an issue for you ?. I am able to reproduce this and it is fixed in v12.13.1

[bzoz]

Fixed in v13 and v12, but still an issue on v10.19.0

[richardlau]

Fixed in v13 and v12, but still an issue on v10.19.0

Any chance you could try the proposed 10.20.0 (#31984) as it brings 10.x up to a more recent libuv: https://nodejs.org/download/rc/v10.20.0-rc.1/

[bzoz]

Yep, fixed in 10.20.0.