Post

bottom line is that transitions around navigate "work", but are short-circuited by useSyncExternalStore used by the router :/. It's a trade-off. FWIW, useDeferredValue on the QueryKey is what works for react-query.

Thanks for the input @tkdodo.eu 👍 We already have a custom version of `useSuspenseQuery` that handles the re-suspension issue but @phry.dev is it possible to do something similar with `useReadQuery`? Or what would be the best pattern to use Suspense with loaders that are driven by url params?

0 reposts1 like

Maybe I'm doing it wrong but adding `.toPromise` doesn't seem to help 😅 I tried even to update to React v19 to get async transition support but that didn't change anything.

Okay this is super embarassing... I swear I tried to use `useDeferredValue` with `useReadQuery` and it didn't work but now that I try it in my repro instead of the project code it actually works and the suspense fallback is not shown 😅 However the `isPending` flag doesn't seem to work 🤔