This Suspense boundary received an update before it finished hydrating.
Probably a more general SSR question. I see a race (I call it that because if I throttle my network it goes away) that causes
when I add Clerk to the React Query Start example.
Here are some small repros, seems like something with about the ClerkProvider modifying state internally during hydration, which could be fine — just trying to figure out if it's expected.
https://github.com/thomasballinger/tanstack-start-react-query-clerk-repro/pull/2
https://github.com/thomasballinger/tanstack-start-react-query-clerk-repro/pull/1
I think I'm looking for guidance on how bad this is and whether it's something to report to Clerk.
I found this when using useSuspenseQuery with Convex and the TanStack Query with TanStack Start, but narrowed it down to just useSuspenseQuery and Clerk.
when I add Clerk to the React Query Start example.
Here are some small repros, seems like something with about the ClerkProvider modifying state internally during hydration, which could be fine — just trying to figure out if it's expected.
https://github.com/thomasballinger/tanstack-start-react-query-clerk-repro/pull/2
https://github.com/thomasballinger/tanstack-start-react-query-clerk-repro/pull/1
I think I'm looking for guidance on how bad this is and whether it's something to report to Clerk.
I found this when using useSuspenseQuery with Convex and the TanStack Query with TanStack Start, but narrowed it down to just useSuspenseQuery and Clerk.
