Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What’s wrong with the in-browser DOM inspector? I’ve never run into a problem with React, it’s output, it’s error messages, or anything else such that I couldn’t trivially dive in and fix. I’ve never once felt the need for React DevTools in my 5 or so years of React.

I remember AngularJS well, that’s a framework I can do without.



Inspecting the state or properties of components. Inspecting the component hierarchy (not always possible to guess it from the DOM). Things like that.


There's a problem when you set breakpoints trough DevTools and instead of Chrome breaking on that line, you end up in some VM1234 file with a bunch of minimized react core code in it.


for me, a lot of it is simply not having to go in and add in console.logs to everything to see what props and state are, you can just explore around instead




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: