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

Extension chokes on sourcemap when debugging addons

Open
#326 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
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript, vscode
Domain
devtools

Research direction

Start by reproducing a debug session for a Parcel-packaged Firefox add-on and inspect the launch definition's pathMappings and logging output. Trace the PathConversion handling of the data:application/json sourcemap URL appended to the generated JavaScript. Done means the session accepts the sourcemap and breakpoints can be set and hit.

Written by the indexing model from the issue text.

Description

bug sourcemaps

Hi,

I'm trying to debug a simple FF add-on that I'm packaging with Parcel. vscode-firefox-debug loads the extension and it runs fine. The problem is I'm unable to set/hit break points.

I played around with many launch configuration pathMappings combinations without success. I then enabled logging in the launch definition and I now get the following error report when I start a debug session:

INFO |000.178|PathConversion: Can't convert url data:application/json;charset=utf-8;base64,eyJtYXBwaW5ncyI6Ijs7...

The problem URL is the data sourcemap URL added at the end of the associated JS file packaged by Parcel.

I don't think the sourcemap URL is corrupted as I can load the Parcel generated JS files using the VSCODE colder.source-map-visualization extension without complaint.

Is there a work round for this?

Cheers, Steve

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.