![Cover image for The definitive guide to JavaScript Debugging [2021 Edition]](https://media2.dev.to/dynamic/image/width=1000,height=420,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Fpli0trzhf8zn59lv4qiq.png)
Introduction
As developers, we’ve traditionally rooted out errors in our programs (we’ll call them bugs from now on if that’s ok) by usi...
For further actions, you may consider blocking this person and/or reporting abuse
Good overview, but somehow I'm still resorting to console.log more often than not ... why? Two reasons:
1) asynchronous code makes "stepping" a pain (stepping into, that is)
2) transpiling (Babel) makes things painful, more often than not I fail at properly setting up source maps
Could be me, but as a result I always find myself reverting to the tried and true "console.log" way.
Thanks, @leob for your thoughts!
For # 1, do you use the
asyncswitch in the debugger tool?For # 2, Oh yes, agree! Especially when the source maps are missing.
Wow, that's a great tip for #1, never hear of that, thanks!
Glad, it helped 🙂
Something I'm excited for is Edge browser has a VS Code extension that incorporates the DOM Elements debug panel into VS Code (IIRC), which is the main reason I still need to use DevTools. I tried and failed to use both the DOM extension and the Source extension; you need some incantation to bring them both online at the same time.
Great content, thank you for sharing it!
Thank you!
This is great. Thanks for sharing such a detailed post!
Thanks a lot Mir! Glad you liked it.
Great post. Learning a lot.
Great thanks! Glad it was useful.