vscode-live-server: Bug in `ChromeDebuggingAttachment` settings
Very nice tool.
Is it possible to use the VSCODE attach to the live server? Or to Launch the Live server from the launch.json . If so , how does one do that? Or is there a fundamental limitation that I have to use the Chrome Debugger (which I really don’t mind, I just wanted to see if I could use the VSCODE debugger also).
Launch.json
{
"version": "0.2.0",
"configurations": [
{
"type": "chrome",
"request": "launch",
"name": "Launch Live Server",
"url": "http://localhost:5500/WorkBench/Workbench.html",
"webRoot": "${workspaceRoot}"
},
{
"type": "chrome",
"request": "attach",
"name": "Attach to Live Server",
"port": 5500,
"webRoot": "${workspaceRoot}"
}
]
}
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 15 (8 by maintainers)
Commits related to this issue
- fixes bug #47 — committed to ritwickdey/vscode-live-server by ritwickdey 7 years ago
- v3.0.1 update with #31 #47 — committed to ritwickdey/vscode-live-server by ritwickdey 7 years ago
Hi I’m not sure if I’m missing something but it still doesn’t seem to work for me and I get that same message:
Cannot connect to runtime process, timeout after 10000 ms - (reason: Cannot connect to the target: connect ECONNREFUSED 127.0.0.1:9222).
What I did was: in setting.json:
"liveServer.settings.ChromeDebuggingAttachment": true
in launch.json:
and In the “target” field of Chrome, appended
--remote-debugging-port=9222
moved to: https://github.com/Microsoft/vscode-chrome-debug/issues/555