fix: settle the promise when the input stream ends

[1yakub]

read() returns a promise that never settles if the input stream ends before a line arrives. There is a handler for line, one for error and one for SIGINT, but none for close, and readline emits close on its own the moment the input hits EOF. Nothing rejects, nothing resolves, so the caller waits on a promise that can never finish. Once nothing else is holding the event loop the process just exits, and whatever was waiting is gone with no error anywhere.

That happens any time stdin is not something a person can type into, which is common: < /dev/null, an already closed pipe, a child process spawned without stdin, most CI shells.

Where I hit it: npm login in a non interactive shell. npm prompts for a username, the prompt can never be answered, and npm exits 1 printing no error at all. Its own debug log says "Exit handler never called! This is an error with npm itself", which is npm noticing that the command promise never resolved. Repro with npm 12.0.2 on Node 22.23.2:

npm login --auth-type=legacy < /dev/null
# prints "Username:", exits 1, no error message

Proof that the promise is the thing left hanging, run against npm's own bundled copy of read:

const { read } = require('read')
let settled = false
process.on('exit', c => console.log(`exit=${c} settled=${settled}`))
read({ prompt: 'Username:' }).then(() => settled = true, () => settled = true)

$ node t.js < /dev/null
Username: exit=0 settled=false

The fix adds the missing close handler and rejects with canceled, the same error SIGINT already uses, since both mean the same thing: no answer is coming. A finished flag keeps the deliberate rl.close() in done() from rejecting a promise that already resolved.

Two tests: one that a stream ending with no line rejects, and one that a stream ending after a line still resolves, which is the case that would break if the close handler fired unconditionally. Without the source change the first test hangs until the runner cancels it and the suite exits 1; with it the suite is 6/6 and lint is clean.

Checked with npm login too: patching only this package inside an installed npm 12.0.2 turns that silent exit 1 into npm error canceled.

Written with AI assistance (Claude Code); the repro, the fix and the test runs are my own and verified locally.