Console.log() has been a reliable and easy way to track down errors and bugs ever since I started learning JS but with extensive usage of states, complex objects, etc it's no longer the fastest way of debugging the app. 

Chrome Dev tools have had a solution for a while and VS Code editor could be connected to it which makes the whole debug process even smoother and faster.

Here is a set of techniques how to find errors faster than with just the console.log() method.

This is a great video with valuable tips on how to debug an app efficiently with console methods, Chrome dev tools, and VS Code.

Youtube

Console.log() has been a reliable and easy way to track down errors and bugs ever since I started learning JS but with extensive usage of states, complex objects, etc it's no longer the fastest way of debugging the app. \nChrome Dev tools have had a solution for a while and VS Code editor could be connected to it which makes the whole debug process even smoother and faster.\nHere is a set of techniques how to find errors faster than with just the console.log() method.\nMore useful console methods\n\nChrome Dev Tools debugging\n\nVS Code debug with Mozilla Dev tools\n\n\n\nThis is a great video with valuable tips on how to debug an app efficiently with console methods, Chrome dev tools, and VS Code.\n\nEssential JavaScript debugging tools for the modern detective by Rebecca Hill | JSConf Budapest 2019\n

Lets stop guessing and debug apps properly with VS Code debugging tool

More useful console methods

Chrome Dev Tools debugging

VS Code debug with Mozilla Dev tools