React Developer Tools

Leanne Goldsmith2023年3月8日

★★★★★1

The chrome extension was working fine and I have no errors in my React.js app in my visual studio code terminal. But now when I go to refresh my webpage, I get the error "Loading React Element Tree... If this seems stuck, please follow the troubleshooting instructions." I have read many solutions, but none seem to work for me. Has anyone experienced this issue before and been able to solve it. Solutions I have tried: updated chrome version remove react dev tools extension and reinstall it restarted computer restored to defaults on my inspect tools

Jason Wisener2023年2月17日

★★★★★1

useless

IW S2023年2月13日

★★★★★1

Angular and Vue don't need an extension because their frameworks actually work with the native chrome inspector tools. Meanwhile, the developers of React, couldnt make their framework work for the native inspector tools so instead of fixing this, they had the idea to make a work-around which is this extension. If the people who made React developed web applications before in their lives, they would have quickly come to the conclusion that React should work with the native inspector tools and that this extension is a 'band-aid' solution. Instead, this lackluster extension was made which doesnt even allow me to properly edit styles in the inspector. That stacked with some React elements not being able to support native css directive classes, like angular & vue, make React a spectacular example of how React is objectively an inferior framework to Vue and Angular. To the React developers, start over with this framework. When you can't decide if you want a component to be a class or a const, a normal component, or an FC component, so you instead try to support all of them at once, you have fundamentally failed at providing any sort of `frame` to work off of. Decide how you want a component to look like and stick with that. I recommend you look at Angular or better Vue to see how simple a component should be, and go from there. Aug 2023 update: The extension has now ceased to work all together. Selection of Dom elements or seeing them in the browser is now completely broken. It's absolutely baffling that React is the most used frontend framework, when it was developed by people with little to no experience in actual frontend framework development. To answer the person who responded: If you inspect a dom element with angular or react by right clicking it and 'Inspecting' you can see the actual custom dom elements that are in your code (<custom-element />) with the inspector tool that chrome provides. Reacts DOM in that same inspector is a jumbled mess, which is why they made this extension to make elements and components actually inspectable. Unfortunately the developers were a little lazy and the extension has a fraction of the inspection capabilities that chrome's natural inspector already has.

Fit Sherlockian2023年2月13日

★★★★★5

thx

Jack Scott2023年1月30日

★★★★★1

I never use this extension and want to disable it from my project. But when I remove it, I get an annoying console message. When I disable the react devtools global hook (to disable the console log message) I get another console message telling me that my fast refresh is now disabled.

Julien Tavernier2023年1月23日

★★★★★3

Dommage que cette extension déclenche des alertes dans la console et notamment concernant les performances..

Matías Bubello (Matt)2022年12月26日

★★★★★1

Funcionaba genial, la última actualización de chrome lo rompió. Esto lo puse en 2022, es increible que no lo hayan actualizado, no se puede testear en el browers más usado del mundo. En el único lugar donde funciona esta extensión es en firefox

Mariela Insaurralde2022年12月21日

★★★★★1

Era muy util hasta que dejo de funcionar. Corregirlo por favor!

Абу Хурайра2022年12月14日

★★★★★1

Во избежание серьезных проблем не рекомендую использовать

Vitalii Onyshchenko2022年12月3日

★★★★★1

Since last update stopped working in Chrome v.100.