You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know there are certainly already opened issues about that but after spending an hour trying to fix my project, and getting pretty upset about it, I think I need some help.
I was using the Chrome extension and everything was fine with debugging components (because that's mainly why it's useful, other parts can be debugged within the browser devtools quite easily).
But recently, it stopped working. The debugger launches, but the breakpoints in the components get jammed to some wrong locations.
The Chrome extension got deprecated in VSCode and it looks like the companion JS debugger can't handle anything. From that, it's already hard for people to find how to work the debugging out. It seems for that the only way to have it launching is using the nightly version. (I have removed the Chrome extension in the meantime...).
That being said, the problem with the breakpoints is still the same. I tried the source map configurations I found on the different sources of information, but the breakpoints always fail.
It is very frustrating and annoying that those problem keep coming now and then everything in VSCode, webpack or whatever change. I'm not on top of those things and it just waste my time at work.
I don't know if there is a right way to do the documentation on the debugging issue - is it my project configuration being wrong? some issue with the JS debugger? But all I can see is that what I find online doesn't work.
Happy to give more details if need.
Thanks,
Pierre
The text was updated successfully, but these errors were encountered:
Hi,
I know there are certainly already opened issues about that but after spending an hour trying to fix my project, and getting pretty upset about it, I think I need some help.
First, it seems the documentation on the VueJS website is out of date (https://v2.vuejs.org/v2/cookbook/debugging-in-vscode.html). Second, the documentation on the GitHub is not right, at least I can't make it work.
I was using the Chrome extension and everything was fine with debugging components (because that's mainly why it's useful, other parts can be debugged within the browser devtools quite easily).
But recently, it stopped working. The debugger launches, but the breakpoints in the components get jammed to some wrong locations.
The Chrome extension got deprecated in VSCode and it looks like the companion JS debugger can't handle anything. From that, it's already hard for people to find how to work the debugging out. It seems for that the only way to have it launching is using the nightly version. (I have removed the Chrome extension in the meantime...).
That being said, the problem with the breakpoints is still the same. I tried the source map configurations I found on the different sources of information, but the breakpoints always fail.
It is very frustrating and annoying that those problem keep coming now and then everything in VSCode, webpack or whatever change. I'm not on top of those things and it just waste my time at work.
I don't know if there is a right way to do the documentation on the debugging issue - is it my project configuration being wrong? some issue with the JS debugger? But all I can see is that what I find online doesn't work.
Happy to give more details if need.
Thanks,
Pierre
The text was updated successfully, but these errors were encountered: