Debugger pwa-chrome configuration does not stop on breakpoints

[izkrivera]

Describe the bug

When running the JS Debugger (nightly v2022.3.717) breakpoints are always off (empty dots). Toggling then on the breakpoints panel turns some of them on (red). However, the breakpoints never pause execution.

Configuration on a Next's / typescript running on the localhost:

"configurations": [
        {
            "name": "Chrome localhost",
            "type": "pwa-chrome",
            "request": "launch",
            "url": "http://app.XXXXXXXX.local:3000",
        }
    ]

To Reproduce
Steps to reproduce the behavior:

1. Add breakpoints to any .tsx file
2. Click on 'Start Debugging'
3. Navigate to where the breakpoint should fire
4. Confirm it does not fire

Log File
vscode-debugadapter-25a5d31c.json.gz

VS Code Version: 1.65.2

Additional context
Next's and Typescript, localhost app.

[connor4312]

This'll be fixed in the upcoming nightly build. Please give it a shot!

[trinoorrod]

In latest VSCode build, this is broken again.
Previously was not broken, applied update today and now I cannot set breakpoints.
{
"name": "DESKTOP: Attach to Chrome",
"port": 9222,
"request": "attach",
"type": "pwa-chrome",
"webRoot": "${workspaceFolder}",
}

[trinoorrod]

Just to add: rolling back to VSCode March 2022 (1.66.2), breakpoints function as normal.

[connor4312]

Sorry, this PR didn't get merged yet. Will ping for reviews on it tomorrow.

[trinoorrod]

No worries. FWIW, on MacOS between VSCode 1.66.2 and 1.67 debug broke.
We've rolled back to 1.66.2, so no biggie right now.
Will try the nightly to see if your fix has resolved whatever issue we're having and let you know.

[connor4312]

You're probably not facing the same issue as the poster as this bug was present and reported on 1.66.

[trinoorrod]

It's definitely the same bug, we've also seen it before. It seems to be one of those issue where fixing it for one case breaks it for others.
However, can confirm js-debug-nightly resolves the issue for us.

[connor4312]

If nightly resolves it you're probably hitting microsoft/vscode#148864

[TylerLeonhardt]

@izkrivera Can you try out the latest insider build of VS Code: http://code.visualstudio.com/insiders if the issue is fixed there, can you please respond with /verified so we can mark this issue as verified to be fixed?