ts-jest (and maybe ts-node) files do not get source mapped when debugging.

[jakebailey]

Describe the bug

When we updated to 1.60 today, we noticed that we couldn't set breakpoints our tests anymore, or if they worked, they'd be on the wrong line, and anything we browsed was the unmapped code (not the original TS source).

To Reproduce

I have created a self-contained reproducer here: https://github.com/jakebailey/ts-jest-vsc-repro

Log File

vscode-debugadapter-2d0009e1.json.gz

VS Code Version: 1.60

Additional context
Add any other context about the problem here.

[connor4312]

Thanks for the issue and repro!

This is due to logic that we added to help with monorepos, where we default to resolving sourcemaps in the nearest package.json-containing directory relative to the program. In this case that meant we only resolve sourcemaps in node_modules/jest.

This'll be fixed in Monday's nightly debugger build. You can also explicitly set outFiles to its default value in your launch.json:

            "outFiles": [
                "${workspaceFolder}/**/*.js",
                "!**/node_modules/**"
            ]

Update: This will also be in the 1.60.1 patch release which we expect to land Monday the 13th

[jakebailey]

Given this regressed VSC 1.60 (which just came out), will this be backported or anything?

[connor4312]

Yes I think I will introduce this as a candidate for 1.60.1.

[sandy081]

Changed to August 2021 recovery milestone so that we can track it from our queries.