react-query-questions
solid-query-questions
table-questions
virtual-questions
router-questions
react-charts-questions
ranger-questions
vue-query-questions
svelte-query-questions
bling-questions
form-questions
angular-query-questions
start-questions
db-questions
start-showcase
router-showcase
📣-announcements
Suspense example has a bug?
Infinite queries fetching behavior (and preventing duplicates/missing data)

global disable all queries n seconds
queryClient.clear() but I also want it to stop fetching for n secondsawait query without fetching it
useQuery for a given query.
In order to handle user input, I need to use that data. I don't want to just error in the event that the data is not yet fetched, or discard the input.
I know I can just use await queryClient.fetchQuery(blah) in the user input handler. but my understanding is that this will make a second network request, if the first one (from the hook) hasn't returned yet. is that true? I know it won't if there's already data that isn't stale....React query serverside prefetching with passing more params to custom function not working

React Query Authentication
Invalidate query doesn't work
Mutations started in offline mode are executed 1-by-1 after going online
How To use useQuery with dependency array ?
useInfiniteQuery pageParams always undefined
How to properly use query key factories with multiple variable keys?
Do I really need useMutation?
Handling optimistic update rollback when multiple mutations have been ran
`staleTime` option prevents optimistic update from rerendering component
someMutation.mutate(), a useQuery hook won't pull in optimistic cache changes made to the cache in the onMutate function of useMutate when a queries' stale time is not 0.
This only seems to manifest itself when the onChange is being triggered by SlateJS, as a regular input doesn't seem to have the same issues.
...Why does invalidateQueries() break mutate()'s onSuccess() sometimes, but not mutateAsync().then() ?
Register query functions react-query
Does react-query ever persist cached values on the client?
Is there a way to force logging of errors in production?
Avoiding state-sync when awaiting response body on error
{ error: 'Invalid password' }.
I'm trying to avoid the onError callback when writing my useQuery/useMutation code (since those callbacks are being deprecated) and this article explains the downsides to how this stuff leads to "state sync" but I can't find any way to avoid it because JSON body doesn't get parsed when there's an error, so I have to do it myself (I'm using ky as the http lib).
If there's an error, it seems like I have to use await error.response.json() to get the actual JSON data and that has to be done inside a callback or a useEffect....Is there a way to set a types for queryClient without casting everytime?