Vue component unverified breakpoints
See original GitHub issueBreakpoints 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' } }
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:8
Top Results From Across the Web
Debug Vue.js App with VS Code. Error Unverified Breakpoint
When I try npm run serve I get the error message unverified breakpoint and my breakpoint is never be hit. I use the...
Read more >“Unverified Breakpoints” when using VS debugger on Vue ...
Problem: I'm getting unverified breakpoints when I set them in my TS files and Vue components while running VS debugger.
Read more >VS Code - Debugging VUE component in Laravel project
This is the configuration that worked for me, it allows me to set breakpoints for .vue and .js files directly in VSCode: VSCode's...
Read more >vscode vue debug unverified breakpoint,
setting debugger statements (on js or vue files) VS Code opens de browser, opens the sourcemap file and stops where the debugger statement...
Read more >Debug Node.js Apps using Visual Studio Code
The Visual Studio Code editor includes Node.js debugging support. ... generated JavaScript, then breakpoints show up as unverified (gray hollow circles).
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have a similar issue. They are all unverified, but partially work.
In my tests, I noticed that all the breakpoints that are meant for a page load do not work. All the others work, although they are unverified.
Further I noticed that the breakpoint is removed on page load and later set again. The way I see it, however, they are set too late. In the logs you can see that.
Steps to reproduce:
debugger;
in a line after the breakpointdebugger
.With this scenario, you can see in the logs that the breakpoint is not set again until after the
pause
event.Line 79: breakpoint removal request Line 104: pause event received (for
debugger
) Line 133: setting breakpoint requestLog file: log.txt
I had a similar issue and eventually became a little suspicious over the fact that my IDE was reporting Debugger for Firefox version as v2.9.1 (in the top header); even though further down in the README.md (ostensibly fetched from Github), the badge says v2.9.6!
I am using VSCodium and rather a noob at this IDE. I eventually figured out that it’s using a different extensions marketplace to VSCode. I raised the issue with OpenVSX registry.
If you are in the same case, you can manually install the correct version by downloading a
.vsix
archive from the M$ marketplace and install it manually into VSCodium.