SourceMaps don't bind on latest next.js version server side (Docker)

Describe the bug Next.js now uses eval-source-map from version 9 onwards. It looks like eval-source-map generates webpack-internal:///./ references.

I added the settings below but it makes no difference:

      "sourceMapPathOverrides": {
        "webpack-internal:///./": "${workspaceFolder}/"
      }

I wonder if https://github.com/microsoft/vscode-js-debug/blob/e2191de3d65c8e90be183bd545ec8441972566a2/src/targets/browser/browserPathResolver.ts#L111-L113 has anything to do with it?

Should webpack-internal:///./ be added to this list? https://github.com/microsoft/vscode-js-debug/blob/4d7737fbb65cf6485bd333e03f5319ceafaa797e/src/configuration.ts#L931-L939

To Reproduce Steps to reproduce the behavior:

1. Clone https://github.com/jasonwilliams/nextjs9-typescript-server-vscode-example
2. yarn install
3. docker-composer up
4. Launch -> launch server (Docker)
5. set a breakpoint in pages/index.tsx

Log File

VS Code Version: 1.51

[connor4312]

Actually, the scenario is narrower than I thought. For data URI sourcemaps, we use the path of the compiled file to see if we should resolve it. I put in a fix to remove the “protocol”, so webpack-internal:///./pages/index.tsx will turn into /pages/index.tsx for matching purposes, which the default glob is capable of dealing with. So I put in a targeted fix.

[connor4312]

@roblourens make sure to remove the sourceMapPathOverrides section as well – apologies for not posting easy verification steps in a long thread:

1. Follow these instructions: https://github.com/microsoft/vscode-js-debug/issues/854#issue-740838182
2. But before step 4, remove these lines https://github.com/jasonwilliams/nextjs9-typescript-server-vscode-example/blob/f404275fb07599b4a8e4135e10d2a8d0fc10163d/.vscode/launch.json#L22-L24

Closing for re-verification attempt