Eddie
Explore posts from serversHydration error when using <Show> in SolidStart
Wrapping the
<Show>
in a <Suspense>
seems to fix the issue for me. That led me to adding the suspense tag in the app.tsx file:
And I don't longer need to have the suspense in the footer component. So, I guess I learned that everything async requires a suspense somewhere up the component tree.12 replies
Hydration error when using <Show> in SolidStart
I tried a fresh browser session, it did not help.
I have been banging my head against this for some time now and can't figure it out, I ended up doing it this way, which works:
If, in the above example, I replace
hasUser()
with user()
in the when
clause, I get the hydration error again.
I would have preferred to put the user()
directly in the when
clause, and I am still wondering if I should have been able to.12 replies
Hydration error when using <Show> in SolidStart
In my case, the resource
user
is preloaded on the route that in turn renders this component, so I assume that when the Footer component function runs, it is already a fulfilled promise.
- Does this mean that deferStream: true
will have no effect here?
- Why, if user()
is fulfilled when this component mounts, is the when
clause in the <Show>
not making the content of the <Show>
not render on mount (and in turn not cause hydration error because the element is there from the get-go)?12 replies