[DevTools Bug]: Standalone DevTools disconnects when selecting a component with large state
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 251k
- Forks
- 51.4k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 53
Description
Website or app
https://github.com/drewhoener/react-standalone-devtools-disconnect-repro
Repro steps
When using standalone devtools and attempting to inspect a component with large props or memoized data, the devtools disconnects.
I assume this is because there's just too much to send over the socket?
This works fine with the devtools extension in chrome and firefox, but fails with standalone.
Follow the instructions in the readme of the linked repro repository, just running and attempting to inspect the element with standalone devtools causes the disconnect
How often does this bug happen?
Every time
DevTools package (automated)
No response
DevTools version (automated)
No response
Error message (automated)
No response
Error call stack (automated)
Error component stack (automated)
GitHub query string (automated)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the README and reproduction steps in the linked react-standalone-devtools-disconnect-repro repository, then reproduce the disconnect while inspecting the component with large props or memoized data. Compare the standalone behavior with the Chrome and Firefox extensions, and consider the work complete when standalone DevTools stays connected during that inspection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100