You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
open Chrome 132.0.6834.84 and load chrome://inspect
open dedicated devtools for node
run "node --inspect"
wait for node to connect to devtools
enter "global." in the devtools console
the autocompletion method list does not pop up
How often does it reproduce? Is there a required condition?
always
What is the expected behavior? Why is that the expected behavior?
The autocompletion method list is expected to pop up as it does for browser objects and as it used to for node:
What do you see instead?
No autocomplete method popup.
Additional information
Since this is working in Chrome 113, it appeared as a Chrome issue and was submitted on the Chrome bug tracker, but was closed with the following response:
This is a Node.js issue. I can reproduce this down to Node 14, but with Node 12 autocompletion works as expected.
The way autocompletion of object properties works is that we evaluate the input, but abort if this evaluation may cause a side effect. Without side effect, we get the object properties and offer these properties as autocomplete options.
From Node 14, side effect check fails. You can easily check this by running Node with node --trace-side-effect-free-evaluate --inspect.
I would suggest you file an issue on the Node issue tracker.
The text was updated successfully, but these errors were encountered:
Version
v22.13.0
Platform
Subsystem
No response
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
always
What is the expected behavior? Why is that the expected behavior?
The autocompletion method list is expected to pop up as it does for browser objects and as it used to for node:
What do you see instead?
No autocomplete method popup.
Additional information
Since this is working in Chrome 113, it appeared as a Chrome issue and was submitted on the Chrome bug tracker, but was closed with the following response:
https://issues.chromium.org/u/2/issues/390205856#comment5
The text was updated successfully, but these errors were encountered: