Debugger and current debugging line are both misplaced
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript, vite, vscode
- Domain
- devtools
Research direction
Use the linked vfd repository and its launch.json to reproduce the issue: run npm install, npm run dev, then set a breakpoint in src/App.vue between lines 5 and 8 and start the Firefox configuration. Compare the debugger position and current debugging line with the working Chrome configuration; done means Firefox stops on the correct source line.
Written by the indexing model from the issue text.
Description
This is the only thing currently keeping me from switching to firefox
Repro steps:
add launch.json from below
npm install
npm run dev
In src/App.vue add a breakpoint between line 5 and 8
Start debugging
I am trying to debug from vscode a vue 3 with TS and vite project
As stated in the docs i did:
open the Developer Tools Settings and check the checkboxes labeled “Enable browser chrome and add-on debugging toolboxes” and “Enable remote debugging”
and executed Firefox as follows
"C:\Program Files\Mozilla Firefox\firefox.exe" -start-debugger-server
The problem is that the debugger is all jumpy and doesn’t hit the correct line:
Here is my launch.json (the one for chrome works perfectly well)
{
"version": "0.2.0",
"configurations": [
{
"type": "chrome",
"request": "attach",
"name": "Attach to Chrome",
"port": 9222,
"webRoot": "${workspaceFolder}",
"urlFilter": "http://127.0.0.1:4000/*"
},
{
"name": "Attach to Firefox",
"type": "firefox",
"request": "attach",
"url": "http://127.0.0.1:4000",
"webRoot": "${workspaceFolder}",
"pathMappings": [
{
"url": "http://127.0.0.1:4000/src",
"path": "${workspaceFolder}/src"
}
]
}
]
}
- Dominant language
- TypeScript
- Stars
- 447
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
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.
More from firefox-devtools/vscode-firefox-debug
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
firefox-devtools/vscode-firefox-debug#391 · 2 comments · 1 reaction ·
-
bug path mapping
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Castle Open
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
Create new issue Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
All issues in firefox-devtools/vscode-firefox-debug
Similar issues
-
blocklist removal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
MetaMask/eth-phishing-detect#296544 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pastelsky/bundlephobia#1122 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
category/development priority/P2 scope/file-operations scope/testing type/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Enatega Customer and Rider app: Add-ons price is not visible to customer after order is placed. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100