Chrome Debugger is BETTER than you might think

Jokes aside, unless you really just need to peek at one value, using the debugger gives you much more context and awareness while debugging your application… and you won’t end up having 7 logs here and there flooding the console.

With Chrome you don’t even need to setup anything. It just works, and you get for free features like conditional breakpoints, watching values, and if you really like logs… you have logpoints!

_______________________________
Hit like and subscribe for more content! :D

You can also follow me on the other platforms:
_______________________________

#debugging #devtools #javascript

[wilfy]

Very nice video, I feel like there's no real consensus on how to debug other than console log etc and also not many videos that cover it online. I learned a lot 😃

[moihugo]

Super helpful, why did I not know about this features until then !! Thanks a lot, that will clearly change the way I write js and ts !

[videoforref]

This is such a useful video. Thank you i am new to front end and react. debugging is essential and how to do it efficiently is something that should be learned first. Glad the yt algo suggested this video.

[rayjazon]

Very well organized and works equally well on VSCode!

[djdankmemes]

Extremely useful video. Thank you for making this!

[JuanMoisesTorrijos]

Great video. This will save me a lot of time!

[farzadmf]

Great video

One thing that I'd add is "never say never" 😉; using `debugger;` could be useful in a couple of use cases: you're not familiar with the code, so you don't know exactly where to put the breakpoint. Or, you have no idea why a line is being executed, so putting `debugger;` in there would definitely help

[ellsonmendesYT]

if ur in dev tools ctrl + p goes to find file, else it goes to print