Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Paths shown in Firefox and VSCode are different

Open
#259 1 comment 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
typescript
Domain
devtools

Research direction

Start with the provided launch.json configurations and reproduce the Parcel 2 beta 3.1 setup in both Firefox and VSCode. Compare how each debugger resolves the source-map paths; done requires determining whether the differing locations are expected and, if not, identifying the debug adapter behavior that needs correction.

Written by the indexing model from the issue text.

Description

Hello, here is a screenshot of the problem:

image

  • Firefox displays the error location according to the source map
  • VSCode displays the real error location
launch.json

I'm using parcel 2 beta 3.1

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "pwa-msedge",
      "request": "launch",
      "name": "Edge",
      "url": "http://localhost:1234",
      "webRoot": "${workspaceFolder}",
      "sourceMapPathOverrides": {
        "/__parcel_source_root/*": "${workspaceFolder}/*",
        "../*": "${webRoot}/*"
      }
    },
    {
      "type": "firefox",
      "request": "launch",
      "name": "Firefox",
      "url": "http://localhost:1234",
      "webRoot": "${workspaceFolder}",
      "reAttach": true,
      "pathMappings": [
        {
          "path": "../*",
          "url": "${webRoot}/*"
        }
      ],
      "clearConsoleOnReload": true,
      "suggestPathMappingWizard": true
    }
  ]
}

Is this behavior normal?

Dominant language
TypeScript
Stars
447
Forks
76
PR merge metrics
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 firefox-devtools/vscode-firefox-debug

All issues in firefox-devtools/vscode-firefox-debug

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.