pwa-node race condition, skipping breakpoints

Describe the bug

In the ‘newest’ version of vscode, pwa-node attach and launch alone with an explicit port defined.

{
    // 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": [
        {
            "name": "Attach",
            "port":51061,
            "request": "attach",
            "skipFiles": [
                "<node_internals>/**"
            ],
            "type": "pwa-node"
        },
        
        {
            "name": "Launch Program",
            "program": "${workspaceFolder}/parseuszips.js",
            "request": "launch",
            "skipFiles": [
                "<node_internals>/**"
            ],
            "type": "pwa-node"
        },   
    ]
}

I have no idea why the debugger is choosing that port, but it does not connect otherwise to the debugging session. Anyway the major issue is in the title, the breakpoints are not hit. And this place is filled with very strange people we dont like.

Anyway, earlier breakpoints are not being hit, the debugging process is not waiting for the ide to attach, Later breakpoints however are reached,

To Reproduce Create pwa-node type for attach and launch in launch,json file under .vscode

Set breakpoints throughout the file

Run the app.

Log File

vscode-debugadapter-0.json.gz

VS Code Version: 1.48.1

[makingglitches]

wouldn’t life be grand if people just left shit stand, not like their constant dodging crap is doing them or anyone else any favors.

[connor4312]

Actually, I was able to repro this in Node 10.1.0, which is what you’re using. This is a known bug in Node, which I thought was fixed by 10.0.0 but is apparently in a minor point release prior to their LTS at 10.13.0. We have not added mitigations in js-debug for this scenario, as doing so is a structural change for a version of Node which is at its end of life.

You can safely update to a more recent Node 10.x version (such as 10.22.0), or update to Node 14 for additional features and performance. This is also advisable in general, as Node 10 versions prior to 10.13 are not LTS and therefore do not receive security updates.