You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FWIW I ran across this while working on updating Replay.io's own support for React 19 by merging down all the last year's worth of changes to our long-running RDT fork:
and then I was inspecting this <SubmitButton> component in a Replay recording of the example app, and observed that I see this error when inspecting it in the recording:
Try inspecting <SubmitButton> and see that we report "can't inspect the component"
I do note that in the getPrimitiveStackCache() function in react-debug-tools, we don't try to warm up Dispatcher.useFormStatus(). Tried adding that myself and rebuilding our RDT fork bundle, but it didn't seem to fix the behavior, so that may not be relevant.
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)
No response
Error component stack (automated)
No response
GitHub query string (automated)
No response
The text was updated successfully, but these errors were encountered:
Website or app
https://github.com/markerikson/react-19-rdt-useformstatus-error
Repro steps
yarn && yarn dev
<SubmitButton>
componentCannot destructure property 'pending' of 'useFormStatus(...)' as it is null.
/cc @hoxyq @eps1lon
FWIW I ran across this while working on updating Replay.io's own support for React 19 by merging down all the last year's worth of changes to our long-running RDT fork:
and then I was inspecting this
<SubmitButton>
component in a Replay recording of the example app, and observed that I see this error when inspecting it in the recording:<SubmitButton>
and see that we report "can't inspect the component"I do note that in the
getPrimitiveStackCache()
function inreact-debug-tools
, we don't try to warm upDispatcher.useFormStatus()
. Tried adding that myself and rebuilding our RDT fork bundle, but it didn't seem to fix the behavior, so that may not be relevant.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)
No response
Error component stack (automated)
No response
GitHub query string (automated)
No response
The text was updated successfully, but these errors were encountered: