source map seems like not work, is there some hints from the perspective of source-map tool?

Open
#516 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
devtools

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.

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

Image

Dominant language
JavaScript
Stars
3.7k
Forks
370
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla/source-map

All issues in mozilla/source-map

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.