microsoft / microsoft/vscode-js-debug
Breakpoints unbound, VSCode cannot find source maps
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 373
- Avg merge
- 1d 9m
- Merged PRs (30d)
- 6
Description
I am unable to get breakpoints working in VSCode when debugging a typescript, angular application. When I look at Debug Diagnostics, it does not find any source location, even though "sourceMap": true is set in the tsconfig.
tsconfig.json
launch.json
Errors in Debug Console:
Sources tab in Chrome Dev Tools:
If I set the breakpoint in Chrome Dev Tools or use the debugger statement in the typescript file, I am able to hit the breakpoint without an issue. How do I get the breakpoints to bind in the VSCode debugger?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the provided tsconfig.json and launch.json, then compare the Debug Diagnostics output with the Chrome DevTools Sources view and Debug Console errors. Done means the TypeScript source locations are found and breakpoints bind in the VSCode debugger for the reported Angular application.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript, vscode
- Domain
- devtools, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100