Repository navigation
readline/promises question results in unsettled top-level await when reading script from stdin #60344
Description
Activity
- changed the title
[-]Promise readline question results in unsettled promise[/-][+]Promise readline question results in unsettled promise when reading script from stdin[/+]on Oct 21, 2025 - changed the title
[-]Promise readline question results in unsettled promise when reading script from stdin[/-][+]readline/promises question results in unsettled top-level await when reading script from stdin[/+]on Oct 21, 2025 What is the expected behavior? Why is that the expected behavior?
Program does not terminate.
Why is that the expected behavior? What do you expect instead?
@aduh95 Why do I expect the program to not terminate? Because the example is pretty much verbatim from https://nodejs.org/api/readline.html#readline where it says:
Once this code is invoked, the Node.js application will not terminate until the readline.Interface is closed
Again, this happens only with
cat test.js | node. So I imagine there's a bug in the stdin/eval handling somewhere.Edit: ah, or do you think this doesn't work because stdin is already used to read in the script so I cannot use it anymore from the script itself?
catcloses the stdin once it has read all the files you passed to it, so to me it seems to be working as expected. To clarify,cat test.js | nodepipes the stdout ofcat test.jsinto the stdin ofnode; if you try to re-use stdin from withinnode, you would find only the script you're trying to run (which is already closed by the timenoderuns the code since it needs to parse the full source before eval).Ah, I'd sort of hoped I could use this to run an interactive installation wizard like
curl https://mywebsite.com/install.js | node. But seems I'll just have to usenpxthen if this is not something node's stdin handling allows. Thanks, feel free to close this then.If you run
curl https://mywebsite.com/install.js | nodeand input stuff in the terminal, it's going tocurl's stdin, notnode's. There's nothing special about Node.js btw, it's just how piping works in POSIX-complient systems.Reacted by Mauro Bieg- added a commit that references this issue
on Sep 5, 2026
Version
v25.0.0 (also reproduced in v24.9.0)
Platform
Subsystem
node:readline/promises
What steps will reproduce the bug?
Place this in
test.js:and run it with:
the above is important.
node test.jsworks fine.How often does it reproduce? Is there a required condition?
Always.
What is the expected behavior? Why is that the expected behavior?
Program does not terminate.
What do you see instead?
Program terminates with exit code 13 and prints:
Additional information
This seems related, but in my case I don't hit Ctrl-C: #53497