Wrong error report message for expression {}) #46877

Activity

1. cola119

   added

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

   on Feb 28, 2023
2. aduh95 commented on Feb 28, 2023

   

   aduh95

   on Feb 28, 2023

   Contributor

   More actions

   Any input that starts with a { and doesn't end with a ; will be wrapped in parentheses:

   node/lib/repl.js

   Lines 417 to 426 in e4e8421

   	// It's confusing for `{ a : 1 }` to be interpreted as a block
   	// statement rather than an object literal. So, we first try
   	// to wrap it in parentheses, so that it will be interpreted as
   	// an expression. Note that if the above condition changes,
   	// lib/internal/repl/utils.js needs to be changed to match.
   	if (RegExpPrototypeExec(/^\s*{/, code) !== null &&
   	RegExpPrototypeExec(/;\s*$/, code) === null) {
   	code = `(${StringPrototypeTrim(code)})\n`;
   	wrappedCmd = true;
   	}

   I think it makes sense for Node.js to show the string it tried to parse rather than the input string – and I think adding those parentheses is useful as well. So if you ask me, I'd say this is not a bug, this is a feature.
3. cola119 commented on Mar 1, 2023

   

   cola119

   on Mar 1, 2023

   Last edited by cola119

   Member

   More actions

   Potentially related issue: #46196
4. jenthone commented on Mar 1, 2023

   

   jenthone

   on Mar 1, 2023

   Contributor

   More actions

   Try to wrap input in parentheses cause another issue:

   $ node
   > {}),({}
   {} // Expected result is Uncaught SyntaxError: Unexpected token ')'
   
5. BridgeAR commented on Sep 11, 2025

   

   BridgeAR

   on Sep 11, 2025

   Member

   More actions

   This got fixed by #59607

   👍React with 👍1Reacted by Xuguang Mei
6. BridgeAR

   closed this as completedon Sep 11, 2025