Using Chromium and Chrome Debugger On Linux
See original GitHub issueUPDATE! I got your extension to open Chromium OK and connect to the debugger 😃:
Maybe you could comment if I did this the best way, and also if there is a way for the Chromium tab to close when the live-server connection is closed? THANKS.
"liveServer.settings.AdvanceCustomBrowserCmdLine": "/usr/bin/chromium-browser --remote-debugging-port=9222"
{
"version": "0.1.0",
"configurations": [
{
"name": "Attach",
"type": "chrome",
"request": "attach",
"port": 9222,
"url": "http://127.0.0.1:5500/",
"webRoot": "${workspaceRoot}"
}
]
}
Hello,
I am trying to use live-server and chrome debugger on Linux with Chromium. If I want to use Chromium rather than Chrome in the debugger my settings used to look something like:
{
"version": "0.2.0",
"configurations": [{
"type": "chrome",
"runtimeExecutable": "/usr/bin/chromium-browser",
"runtimeArgs": [
"--remote-debugging-port=9222"
],
"request": "launch",
"name": "Chromium against localhost",
"url": "http://localhost:8080",
"webRoot": "${workspaceRoot}",
"sourceMaps": false,
"smartStep": false
}]
}
but in live server when I try to make it open changing the preferences to:
"liveServer.settings.ChromeDebuggingAttachment": true,
"liveServer.settings.CustomBrowser": "chrome",
then nothing happens as live-server can’t know to open Chromium.
Can you add an option for Chromium, or is there something I can do? If I type ‘chromium’ on my command line it does not run at the moment as it’s not in the PATH. I can fix that if needed, but being able to point to the executable in your extension could be cool too.
Cheers!
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (2 by maintainers)
Top GitHub Comments
@DzenetanMassart Yes, I have been using it for ages on Fedora. In VS Code settings I have:
So… and now, can we use Live Server with Chromium?