I'm seeing a similar issue as #6, #198, and #212. My setup:

• VS code v1.43.0
• Chrome: 78.0.3904.130
• Node.js: 12.8.1
• V8: 7.8.279.23-electron.0
• OS: Windows_NT x64 10.0.14393
• Debugger for Chrome: 4.12.6

Steps to Reproduce:

• I created a new angular 9 project using ng new
• I added the following launch.json and tasks.json files to my project
• I run the "ng serve" debug configuration, everything works fine and I can hit breakpoints no problem
• When I introduce a simple error in the code, it throws an error with a stack trace
• In the chrome inspection tools, the stack trace is rendered just fine with paths & links back through webpack to the associated source code. Clicking on those links opens the correct file/line.
• In VS Code, the stack trace is rendered with links to files on localhost:4200/... (see attached screenshot)

Here is my launch.json configuration:

{
	"name": "ng serve",
	"type": "chrome",
	"request": "launch",
	"preLaunchTask": "npm: start",
	"url": "http://localhost:4200/#",
	"webRoot": "${workspaceFolder}",
	"sourceMapPathOverrides": {
		"webpack:/*": "${webRoot}/*",
		"/./*": "${webRoot}/*",
		"/src/*": "${webRoot}/*",
		"/*": "*",
		"/./~/*": "${webRoot}/node_modules/*"
	}
}

From the issues mentioned above, it sounded like this was fixed and shouldn't be happening anymore, I believe I'm on the latest projects. Please let me know if I can provide any further information!