Reputation: 974
Chrome debugger jumps to wrong file on breakpoint
I got a vue-js application with multiple components called index.vue, some nested, loaded at the same time. When I set a breakpoint in Chrome inspector in one of the index.vue files, the debugger halts correctly but opens up the wrong index.vue files. It seems to be related to Webpack sourcemaps config as turning this off files are opened correctly in debugger.
Upvotes: 4
Views: 770
Answers (1)
Reputation: 124
This happened to me too as I was fooling around with debugger keyword. Looks like that throughout the breakpoints chain, if you re-run with an extra (or missing if you have more than 1) debugger keyword, then the breakpoint stops on the correct file! Crazy dirty workaround but it seems to work for me when not even disabling chrome cache did.
Upvotes: 1
Related Questions
- Visual Studio Code breakpoint appearing in wrong place
- Debugging Vue in VScode and Chrome, unbound breakpoint
- Debug vue-cli project - no breakpoints, console links to wrong files
- Debug Vue.js App with VS Code. Error Unverified Breakpoint
- How to debug a VueJS 3 Typescript project with VS Code and Chrome using SourceMaps (with Vue CLI and Webpack)?
- Cannot debug Vue app in Chrome with Visual Studio Code - Unbounded Break Points
- debug-vuejs-from-vs-code: unbound breakpoint when debugging vueJS app in chrome
- Debugger settings for Chrome in VS Code with Vue.js
- Breakpoints in files in chrome not being hit when using webpack sourcemaps
- webpack eval-source-map makes chrome breakpoint not working