Different behavior of { a: 1 } in the REPL and the debugger

[tuannd89]

Version

v19.7.0

Platform

No response

Subsystem

No response

What steps will reproduce the bug?

Evaluating { a: 1 } in the REPL and the debugger have different result

% node
> { a: 1 }
{ a: 1 }

% node inspect app.js
debug> { a: 1 }
1

How often does it reproduce? Is there a required condition?

Always

What is the expected behavior?

Like REPL, the result of debugger will be

% node inspect app.js
debug> { a: 1 }
{ a: 1 }

What do you see instead?

% node inspect app.js
debug> { a: 1 }
1

Additional information

The results of { a: 1 } in other runtimes:

• ChromeDevTools: { a: 1 }

• Safari WebInspector: { a: 1 }

We have a similar bug (#45964) but we have not fixed yet and it was closed

[bnoordhuis]

We have a similar bug (#45964) but we have not fixed yet and it was closed

That's because it's not considered a bug but working as expected, it's a deliberate choice. Thanks for the report but I'm going to go ahead and close it.

[cola119]

@bnoordhuis We reached the consensus that it's not a bug, so the node inspect REPL should have the same behavior.

Current:

% node
> { a: 1 }
{ a: 1 }

% node inspect app.js
debug> { a: 1 }
1

Expected:

% node
> { a: 1 }
{ a: 1 }

% node inspect app.js
debug> { a: 1 }
{ a: 1 }

[bnoordhuis]

@cola119 who is "we"?

[cola119]

I meant that we have reached the consensus that the REPL's evaluation of {a: 1} as {a: 1} instead of 1 is not a bug, so node inspect's REPL should behave in the same way.