REPL spamming and stuck when Promise.any([]). is typed #65581

Activity

1. MikeMcC399 commented on Aug 27, 2026

   

   MikeMcC399

   on Aug 27, 2026

   Contributor

   More actions

   This issue is very similar to #64523

   #64034 provided a semver-major fix
2. lazerg commented on Aug 27, 2026

   

   lazerg

   on Aug 27, 2026

   Contributor

   More actions

   This one looks specific to v22. There the completer picks the receiver out with a regex (simpleExpressionRE in lib/repl.js) and evaluates it, so Promise.any([]) really runs while you type. Every run creates a new rejected promise, printing the unhandled rejection redraws the line, and the redraw runs completion again.

   v24 replaced that regex with an AST walk that refuses to evaluate call expressions, in #59774. You can see the difference without a terminal:

   const repl = require('node:repl');
   const { PassThrough } = require('node:stream');
   let calls = 0;
   globalThis.mark = () => { calls++; return {}; };
   const out = new PassThrough(); out.resume();
   repl.start({ input: new PassThrough(), output: out, terminal: false, useGlobal: true })
     .complete('mark().', () => console.log(process.version, calls));

   v22.23.2 prints 1, v24.19.0 and v26.7.0 print 0.

   That PR is labelled backport-requested-v22.x and hasn't landed on v22.x-staging, so v22 keeps the old code path for now. Whether it gets backported is a release team call.

   The import(""). case in #64523 is a separate path, fixed on main by the semver-major #64034, so v24 and v26 still loop on that one.

   👍React with 👍1Reacted by Aviv Keller
3. avivkeller

   added

   v22.xIssues that can be reproduced on v22.x or PRs targeting the v22.x-staging branch.Issues that can be reproduced on v22.x or PRs targeting the v22.x-staging branch.

   on Sep 8, 2026
4. avivkeller

   added

   replIssues and PRs related to the REPL subsystem.Issues and PRs related to the REPL subsystem.

   on Sep 25, 2026