source map seems like not work, is there some hints from the perspective of source-map tool?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.7k
- Forks
- 370
- PR merge metrics
- No merged PRs in 30d
Description
Does this issue occur when all extensions are disabled?: Yes/No
VS Code Version: 1.98.2
OS Version: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36
Steps to Reproduce:
access https://vscode.dev/ for preview
open DevTool of chrome for browsing the Authored source map, and I find out some file couldn't add breakpoints for source-level debugging, there's a case below
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
Reproduce the report by opening vscode.dev in Chrome and inspecting the Authored source map in Chrome DevTools. Compare the files that accept source-level breakpoints with those that do not, then identify whether the source-map data or its consumption is responsible. Done means a reproducible cause and a clearly scoped fix or follow-up are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100