Replies: 19 comments 12 replies
-
Shouldn't the development build be run on |
Beta Was this translation helpful? Give feedback.
-
I am also experiencing this issue, using |
Beta Was this translation helpful? Give feedback.
-
I'm too experiencing this issue. No components are visible in react devtools.
|
Beta Was this translation helpful? Give feedback.
-
Do we have any update on this? |
Beta Was this translation helpful? Give feedback.
-
I'm having this issue as well, and need to be able to showcase dev tooling in a pitch for React. |
Beta Was this translation helpful? Give feedback.
-
FYI. this issue is still relevant as I am also unable to see components tree in React devtools when running |
Beta Was this translation helpful? Give feedback.
-
Turned off PWA (next-pwa), that worked for me. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Having the same issue, the react devtools extension works fine on the react website so it's not my browser. |
Beta Was this translation helpful? Give feedback.
-
Same issue here, still relevant! |
Beta Was this translation helpful? Give feedback.
-
For me this issue was tied to me using preact in which case you'll need to install the preact devtools |
Beta Was this translation helpful? Give feedback.
-
Still an issue 2.5 years later on http://localhost:3000/ React dev tools > Components says:
In chrome://extensions there is no "service worker (inactive)". Chrome is at the latest version, 112.0.5615.138. Not using preact, React dev tools are working on other websites. |
Beta Was this translation helpful? Give feedback.
-
"Looks like this page doesn't have React, or it hasn't been loaded yet." :( |
Beta Was this translation helpful? Give feedback.
-
I had this issue on Chrome (v120) Next version 13.0.5, switching browsers to Firefox & using the Firefox React Devtools extension resolved the issue. |
Beta Was this translation helpful? Give feedback.
-
Still an issue for me with react devtools 5.0.0, chromium 120.0.6099.109 (Official Build) built on Debian 12.4, running on Debian 12.4 (64-bit), react 18.2.0. React DevTools worked for me a while not too far back (weeks maybe?), with the same react version. So it's probably some upgrade that broke it (chromium most probably...? debian was bumped from 12.2 to 12.3 and then quickly to 12.4 and that probably brought in a new chromium version). |
Beta Was this translation helpful? Give feedback.
-
React devtools now works for me again in chromium on debian 12.4. The version and build reported by the browser is still the same (Version 120.0.6099.216 (Official Build) built on Debian 12.4, running on Debian 12.4 (64-bit)), but I know the .deb package(s) have been updated at least once (though I haven't kept track of the exact package version used. The current debian package version of chromium is 120.0.6099.216-1~deb12u1, and here react devtools works for me). |
Beta Was this translation helpful? Give feedback.
-
I have to correct myself: the react devtools works for releases of https://github.com/steinarb/oldalbum (i.e. it works here https://oldalbum.bang.priv.no ) but not for dev versions of the same application. But for other webapps with the exact same software stack and same versions of everything the react devtools work fine in both local dev mode and in released/deployed versions. The webpack file says development. But there is no difference in the result for releases or development versions in my setup: it's delivered as an HTML file loading a bundle.js file whether I'm running in the dev setup or in production: no node.js involved after the webpack'ing. So: weird! |
Beta Was this translation helpful? Give feedback.
-
FWIW I had the problem without running a node.js server. I had the problem with a statically served bundle.js. |
Beta Was this translation helpful? Give feedback.
-
Bug report
Describe the bug
The React Dev Tools don't show any components when I am running a development build. However they show the minified components when running a production build. This has only happened recently (sadly I don't know when it started). There are also no relevant errors in the console or network tab so I can't seem to debug why this is happening.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
When I run
yarn build
with this script:"build": "cross-env NODE_ENV=development next build",
I see a blank "Components" tab in Chrome.When I run
yarn build
with this script:"build": "cross-env NODE_ENV=production next build",
, I see the minified components in the React dev tools.Expected behavior
I would see the React components like I used to.
Screenshots
System information
Beta Was this translation helpful? Give feedback.
All reactions