Yes, yes, I understand.
Current VS Code version is 1.25.1 Mocha version: 4.0.1
Mocha running through launch.json:
{
"name": "mocha",
"protocol": "inspector",
"type": "node",
"request": "launch",
"program": "${workspaceRoot}/node_modules/mocha/bin/_mocha",
"stopOnEntry": false,
"args": ["--no-timeouts", "--colors"], //you can specify paths to specific tests here
"cwd": "${workspaceRoot}",
"runtimeExecutable": null,
"env": {
"NODE_ENV": "testing"
},
"sourceMaps": true,
"outFiles": [
"${workspaceRoot}/dist"
],
}
If you set a breakpoint in a file, it may open another tab with the same file title as "read-only inlined content from source map" and misaligned breakpoints. Also, if you try to edit the file, you realize it's not possible.
After trying out different solutions unsuccessfully, disabling sourceMap by setting it to false did the trick for me:
"sourceMaps": false,
Note: The "outFiles" configuration did not have any effect and was part of my trial and error process, including attempting to build a map to /dist.
I'm unsure about what caused the change in my setup/configuration. I recently updated to vscode 1.25, but I cannot pinpoint the exact reason.
This answer contrasts the discussion on Breakpoints and debugging statements opening "read-only inlined content" available at this link.
Best of luck!