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
I did a CodePen testing the ContainerQuery component with React 17, and it works, so there's no immediate issue there.
Downgrading to React 16.14.0 resolves the issue, so it is something to do with that upgrade. I notice that design-system is still using v16 of react-dom, which reportedly can cause this error. I'll put everything back to v17 & report back…
Browser and operating system used (if applicable)
All of them.
The text was updated successfully, but these errors were encountered:
What happened?
If you load, test.metagame.wtf/dashboard currently, it dies with a 500 server error.
What did you expect to happen?
The page to load correctly.
How can we reproduce the problem (as minimally as possible)?
Visit test.metagame.wtf/dashboard.
Is there anything else we need to know?
I did some tracing on the root error,
Unable to find node on an unmounted component.
, locally, and it seems to be theReactDOM.findDOMNode
of:in
react-container-query
. This may be related to the recent upgrade to React 17.I did a CodePen testing the
ContainerQuery
component with React 17, and it works, so there's no immediate issue there.Downgrading to React 16.14.0 resolves the issue, so it is something to do with that upgrade. I notice that
design-system
is still using v16 ofreact-dom
, which reportedly can cause this error. I'll put everything back to v17 & report back…Browser and operating system used (if applicable)
All of them.
The text was updated successfully, but these errors were encountered: