REPL spamming and stuck when `Promise.any([]).` is typed
Open
Nobody has claimed this yet.
v22.x
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
Version
v22.23.2
Platform
Darwin Aris-MacBook-Pro.local 25.5.0 Darwin Kernel Version 25.5.0: Tue Jun 9 22:28:34 PDT 2026; root:xnu-12377.121.10~1/RELEASE_ARM64_T6041 arm64
Subsystem
No response
What steps will reproduce the bug?
- Open repl by typing
node - Type
Promise.any([]) - Add dot in the end to make it
Promise.any([]). - Repl gets into some infinite loop and prints messages constantly, sometimes unable to exit without killing process separately
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior? Why is that the expected behavior?
Don't print same message infinitely
What do you see instead?
https://github.com/user-attachments/assets/78e1ef27-bd9e-4567-8030-bc7ad3fada96
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in the Node.js REPL with Promise.any([])., then trace the REPL handling for incomplete member access and repeated evaluation. Done means the input does not print the same message indefinitely and the REPL remains normally interruptible without killing the process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100