We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please checkout the linked branch not main https://github.com/eps1lon/react-devtools-repro-no-matching-node/tree/repro/elements-leaking Repro steps and screen recording included in the repro
main
useEffect
Component
Every time
No response
Could not inspect element with id 4
Might be a duplicate of #21436 (comment) since the repro steps are the same. But depending on what the effect is doing, the behavior is different.
The text was updated successfully, but these errors were encountered:
I think this might be the same issue I've captured in a test: #21436 (comment)
Sorry, something went wrong.
I think #21506 might be one way to fix this issue.
Resolved by #21516
bvaughn
Successfully merging a pull request may close this issue.
Website or app
Please checkout the linked branch not
main
https://github.com/eps1lon/react-devtools-repro-no-matching-node/tree/repro/elements-leaking
Repro steps and screen recording included in the repro
Repro steps
useEffect
block i.e. add an effectComponent
elementuseEffect
block i.e. remove the effectHow often does this bug happen?
Every time
DevTools package (automated)
No response
DevTools version (automated)
No response
Error message (automated)
Could not inspect element with id 4
Error call stack (automated)
No response
Error component stack (automated)
No response
GitHub query string (automated)
No response
Might be a duplicate of #21436 (comment) since the repro steps are the same. But depending on what the effect is doing, the behavior is different.
The text was updated successfully, but these errors were encountered: