I'm running into this issue as well, but couldn't see anything that jumped out when running with log at debug. Happy to help troubleshoot, but could use some help getting pointed in the right direction. Chrome/Edge work-out-of-the-box, but like layday mentioned, Firefox doesn't appear to be sending Webpack URLs at all for the vscode debugger to map.

abz041 commented 2 years ago

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "type": "firefox",
            "request": "launch",
            "reAttach": true,
            "name": "Launch localhost",
            "url": "http://localhost/index.html",
            "webRoot": "${workspaceFolder}"
        },
        {
            "type": "pwa-chrome",
            "request": "launch",
            "name": "Launch Chrome against localhost",
            "url": "http://localhost:8080",
            "webRoot": "${workspaceFolder}"
        }
    ]
}

Originally posted by @MetricMike in https://github.com/firefox-devtools/vscode-firefox-debug/issues/271#issuecomment-1014777276

ruffin-- commented 2 years ago

Maybe edit the title? ;^D

Wait, is this just a comment accidentally turned into an issue? Can we close/delete?

hbenl commented 2 years ago

Apparently this is not an issue with this extension, see https://github.com/firefox-devtools/vscode-firefox-debug/issues/271#issuecomment-1046109776

firefox-devtools / vscode-firefox-debug