Chrome devtools console method autocompletion for node is not working
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- JavaScript
- Estrellas
- 122k
- Forks
- 37.3k
- Merge medio
- 4 d 2 h
- PR fusionados (30 d)
- 283
Descripción
Version
v22.13.0
Platform
Microsoft Windows NT 10.0.19045.0 x64
Subsystem
No response
What steps will reproduce the bug?
- 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:
https://issues.chromium.org/u/2/issues/390205856#comment5
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.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Reproducir con Node v22.13.0 usando node --inspect, Chrome 132 y global. en la consola dedicada de DevTools. Compararlo con node --trace-side-effect-free-evaluate --inspect y rastrear la ruta de evaluación de efectos secundarios del autocompletado del inspector; se considera terminado cuando vuelvan a aparecer las compleciones de métodos para global..
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- devtools, javascript, nodejs
- Área
- developer-experience, devtools
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 52/100