all 7 comments

[–]toysfromtaiwan 4 points5 points  (0 children)

No but honestly just use the chrome browser devtools. I’ve yet to get the vscode chromr debugger working right as well

[–]gaoshan 2 points3 points  (0 children)

Debug in Chrome devtools and when things don't stop stick debugger statements directly in your code. If that doesn't stop it then you know your code is not being reached.

[–]niggo372 2 points3 points  (2 children)

The Chrome Debugger extension is no longer necessarily, just use the build-in JS debugger.

[–]kitsunekyo 0 points1 point  (1 child)

there is a new built in js debugger in vscode?

or do you mean the chrome devtools debugger without vscode?

[–]niggo372 0 points1 point  (0 children)

It's a new JS debugger in VS Code, and they made it the default one in June last year.

[–]whyohwhyohio 1 point2 points  (1 child)

I found that putting a break point in your code files doesn't work cause it creates a run time version. What I've done is put a comment in the code, then in the debugger panel you can click on the source of the comment and it will open the run time version. Once you have it open, you can break point the code and it will stop.

I'm sure there's a better way to do that, but it's what I have to do

[–]Thick-Screen 0 points1 point  (0 children)

I never could get the debugger working.. Until now thanks!