Replies: 1 comment 1 reply
-
This is an repro of the issue we're facing. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
After bumping
wagmi
to0.3.5
in our project, we started to face a number of styling issues (here's an example 😆) due to a mismatch between the server-rendered HTML and the first render on the client side.After some investigation, I discovered that this was due to hooks like
useAccount
returningisLoading
astrue
during SSR, but asfalse
on the client. Here's an example of the return value ofuseAccount
during SSR and on the client:Before we upgraded to
0.3
, the SSR and client output was consistent on first render. In this case it returned:A few questions:
true
on the server side. In my tests, it's also true whenautoConnect
is set tofalse
?I appreciate that this isn't necessarily a bug, but more of a side-effect that's having a knock-on effect at our end. I would guess that anyone using Next.js + WAGMI + Stitches will face a similar issue to us.
Beta Was this translation helpful? Give feedback.
All reactions