extensionHost can't bind breakpoints

[Johannes-B-stock]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.60.2
• OS Version: Windows 10 20H2

Hi vscode team,
I am developing multiple extensions and debug it by running the extensionHost like documented in the vscode docs. Unfortunately since a couple weeks ago the extension host cannot bind any breakpoints anymore. It might be since the vscode 1.60 version, but I'm not sure. I checked the issue microsoft/vscode-js-debug#1100 but the proposed help didn't work for me.

This is my launch.json configuration:

  "name": "Extension",
  "type": "extensionHost",
  "request": "launch",
  "args": [
    "--extensionDevelopmentPath=${workspaceFolder}",
    "--disable-extensions",
    "${workspaceFolder}/src/tests/sampleworkspace"
  ],
  "outFiles": ["${workspaceFolder}/**/*.js", "!**/node_modules/**"]

[connor4312]

Please post reproduction steps

/neesdMoreInfo

[Johannes-B-stock]

Hm... After a bit more research I found out that it was actually a setting in the webpack config, namely the "output.devtoolModuleFilenameTemplate". After removing it, the debugging worked again while running the extension in the extension host.
Weird thing is, I have that config since I started writing the extension and debugging always worked, just recently it stopped working.

Thanks for replying anyways...

[connor4312]

Can you share what it was set to?

We made the new debugger the default in 1.60, and there may have been a slight difference in behavior.

[Johannes-B-stock]

It was set to '../../[resource-path]', but I had in a sub folder, not the root folder of the repo.