SSR error when not using SSR
'Expected to find a TSR_DEHYDRATED property on window... but we did not. Did you forget to render <DehydrateRouter /> in your app?', however i am not ussing SSR.
Any idea what might be triggering this? the call to hydrate is checking
which makes sense as my code is executing on the client/chrome so its defined. So it looks like your checking if the document is undefined as a check for is the code on a server. But just because it is in chrome doesn't mean it should be hydrated.
which makes sense as my code is executing on the client/chrome so its defined. So it looks like your checking if the document is undefined as a check for is the code on a server. But just because it is in chrome doesn't mean it should be hydrated.
3 Replies
xenial-black•3y ago
This is fixed in the latest release.
multiple-amethystOP•3y ago
@Tanner Linsley I think the issue was also I did not have an "Outlet" in my root route component. I had imported the Outlet icon from MUI much to my suprise. I was seeing the outlet icon rendered and not my component. That along with the error made for some very confusing debuging.
xenial-black•3y ago
Regardless, it was a bug on my end 😉 thanks