source maps from packages in node_modules don't work in the debugger

[DetachHead]

Version

v18.10.0

Platform

Microsoft Windows NT 10.0.19044.0 x64

Subsystem

No response

What steps will reproduce the bug?

1. create a .ts file that imports from a package that includes the source code and source maps, for example:

   // main.ts
   import { exactly } from '@detachhead/ts-helpers/dist/functions/misc'
   exactly(1 as number, 2 as number)

2. compile it with typescript: tsc main.ts --sourcemap
3. in vscode, set a breakpoint on the exactly function call
4. run it with the nodejs debug console in vscode: node main.js
5. when the breakpoint is reached, hit F11 to step into the function

How often does it reproduce? Is there a required condition?

every time

What is the expected behavior?

steps into the source code located at ./node_modules/@detachhead/ts-helpers/src/functions/misc.ts, as the @detachhead/ts-helpers package includes its source code and source maps

What do you see instead?

stepped into compiled .js file

Additional information

debugging in webstorm produces a slightly different result. instead of stepping into the .js file when pressing "step into", it just steps over instead

[Trott]

@nodejs/tooling (Maybe there's a better team to ping? I basically looked at the teams that @bcoe is on and picked the one that seemed the most plausibly related to source maps.)

[bcoe]

This might be a good opportunity for a contribution from someone who uses vscode and Node.js, I'm unlikely to have any time to dig into this.

[DetachHead]

a workaround is to create a launch config to run your script, specifying the node_modules directory in resolveSourceMapLocations:

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch TypeScript",
            "type": "node",
            "request": "launch",
            "program": "dist/main.js",
            "outFiles": ["${workspaceFolder}/dist/**/*.js"],
            "resolveSourceMapLocations": [
                "${workspaceFolder}/dist/**/*",
                "${workspaceFolder}/node_modules/**/*"
            ]
        }
    ]
}

however having to create launch configs is inconvenient. i'm not sure anymore whether this a node or vscode issue, so let me know if you think i should raise it there instead.

[huseyinacacak-janea]

Hi @DetachHead, this seems to be an issue with VSCode, not Node. You already provided a fix and it looks like it's working successfully. Moreover, you can find more information about Node.js debugging here.
Do you think this issue can be closed now?

[DetachHead]

raised microsoft/vscode#240356