Open RyanEwen opened 4 years ago
Related issue in Debugger for Chrome: https://github.com/microsoft/vscode-chrome-debug/issues/894
As discovered in the related issue linked above, the correct setting for me is "webRoot": "${workspaceRoot}/.."
(I should have realized that webRoot
in fact means the web server's root.. the one served when there's no path in the URL.. duh..). However this still doesn't work over here in Edge land.
I've edited the OP with the proper settings and the logs that show up with them.
I'm guessing based on the logs that this isn't a bug and extension just hasn't been updated to work with remote servers yet.
Coming back to this again and sad to see it still not working.
I noticed this in the trace:
[18:13:48.778 UTC] SourceMaps.scriptParsed: https://localhost:8443/rewen/babeljs/login.js?t=2020-04-24 was just loaded and has mapped sources: ["c:\\var\\www\\html\\rewen\\login.js"]
I wouldn't be surprised if the issue is this c:\\
that's being prefixed to a linux path.
I have a remote Apache server hosting static files, but am unable to get breakpoints to be hit. The log shows that paths are being resolved okay.
This is working with Debugger for Chrome.
Web server (with URL such as https://blah.com/test) has files like so:
Contents of
index.html
:Contents of
test.js
:Contents of
launch.json
:Output of
.scripts
:Contents of
vscode-chrome-debug.txt
: