Vue component unverified breakpoints
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
- Domain
- devtools
Research direction
Start by reproducing the Vue 3 TypeScript setup from launch.json and vue.config.js, then inspect the attached log.txt and compare breakpoint behavior in app.vue with files in the components folder. The issue is resolved when breakpoints in component files are verified and the relevant source mappings work consistently.
Written by the indexing model from the issue text.
Description
Breakpoints in my vue component are all unverified
launch.json is as follows:
"version": "0.2.0",
"configurations": [
{
"type": "firefox",
"request": "launch",
"name": "vuejs: firefox",
"url": "http://localhost:8080",
"webRoot": "${workspaceFolder}",
"log": {
"fileName": "${workspaceFolder}/log.txt",
"fileLevel": {
"default": "Debug"
}
},
"pathMappings": [
{
"url": "webpack:///src",
"path": "${webRoot}"
}
],
"skipFiles": [ // optional
"${workspaceFolder}/node_modules/**"
]
}
]
Tried numerous pathmapping configs but none seem to work with any component.
Using the loaded scripts tab and checking the logs it seems everything is being mapped correctly, even without pathMappings being set.
Oddly enough if i set a breakpoint in app.vue in the src folder it does actually work but no breakpoints in any file in the components folder work.
Log attached for your pleasure.
Other relevant info:
- using vue 3, whole app is typescript
- firefox 93.0
- extension version 2.9.4
- npm version 8.1.0
- everything on pop!_os 21.04 (basically ubuntu 21.04)
edit:
forgot to mention, vue.config.js is set correctly to:
module.exports = {
configureWebpack: {
devtool: 'source-map'
}
}
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mksglu/context-mode#1200 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jaegertracing/jaeger-ui#4506 ·
-
area:desktop area:ui bug platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
anthropics/claude-code#96687 ·
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
AOSSIE-Org/DebateAI#582 · 2 comments ·