Inicio Explorar Ayuda
Registro Iniciar sesión
itk.academy
/
itk-extension
1
0
Fork 0
Archivos Incidencias 0 Pull Requests 0 Wiki
Árbol: 4ea2f41bc1
Ramas Etiquetas
itk-extension
/
l4-LOCAL_VS_CODE
/
.openvscode-server
/
extensions
/
ms-vscode.js-debug-companion
Your Name 078c4cccd0 Default commit hace 4 días
..
out 078c4cccd0 Default commit hace 4 días
resources 078c4cccd0 Default commit hace 4 días
LICENSE.txt 078c4cccd0 Default commit hace 4 días
README.md 078c4cccd0 Default commit hace 4 días
SECURITY.md 078c4cccd0 Default commit hace 4 días
ThirdPartyNotices.txt 078c4cccd0 Default commit hace 4 días
ci.yml 078c4cccd0 Default commit hace 4 días
eslint.config.mjs 078c4cccd0 Default commit hace 4 días
package.json 078c4cccd0 Default commit hace 4 días

README.md

js-debug-companion

A companion extension to js-debug to enable remote Chrome debugging. You probably don't want to install this extension by itself, but for your interest, this is what it does.

The scenario is if you are developing in a remote environment—like WSL, a container, ssh, or VS Codespaces—and are port-forwarding a server to develop (and debug) in a browser locally. For remote development, VS Code runs two sets of extensions: one on the remote machine, and one on your local computer. js-debug is a "workspace" extension that runs on the remote machine, but we need to launch and talk to Chrome locally.

That's where this companion extension comes in. This helper extension runs on the local machine (in the "UI") and registers a command that js-debug can call to launch a server. js-debug requests a port to be forwarded for debug traffic, and once launching a browser the companion will connect to and forward traffic over that socket.