JavaScript debuggers are broken, and it’s our fault

While I now build apps with “Pause on exception” turned on in Chrome Dev Tools and drop debugger statements all over my code base while building out the initial scaffold of features and apps, for my first 2 – 3 years of work with Javascript I used a combination of statements and commenting out lines. Even for code that isn’t quite so far abstracted as React, layers of function calls through libraries makes using the debugger more and more cumbersome as we use higher-level abstractions. To add to our list of feedback for Javascript debuggers here’s a couple more frustrations you may be familiar with:

We can’t really blame the Chrome Dev Tools team for not giving us a better debugger with APIs to declare how to navigate the code base.

Source: samdesota.com