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
Server side query caching with TanStack Start and Query
how can I infer type from queryFn for colDef
Preventing waterfalls for (mostly) static data?
Looking for work as a Frontend developer
Project structure with a global loading gate (data is required to be available after a point)
useSuspenseQuery and Suspense for my use case?..."Nesting" mutations?
useUpdate which does a mutation and invalidates some queries in the onSuccess.
I've got another useArchive which is really just an update, and should do the same invalidations as useUpdate, but then also a few more things (like some other invalidations) in its own onSuccess.
But then I've got a third Sidebar component, which uses useArchive in an event handler, and then has its own onSuccess logic (e.g., close the sidebar)....TanStack Start blocking custom local subdomain
queryOptions dependancies

Question about using React Query as a global store
prefetchQuery vs ensureQueryData in SSR
Tanstack DB - Live Queries return zero results sometimes
isPending always true in react-native
Best approach’s to to ‘derived collection’?
How can I get the returned type from select
Best practice around using `useDeferredValue` on mutation status?
idle to pending to error.
From what I can tell, using const deferredStatus = useDeferredValue(mutation.status) solves this flashing issue perfectly! Unfortunately, it means that I don't get the type narrowing of the original mutation when trying to use it within the conditional render. Is that just something I have to accept and work around?
I tried wrapping the whole mutation i.e. useDeferredValue(mutation), which seemed to work, but it felt wrong to do that given that it's not really a scalar primitive value as suggested by the React docs to use...How to optimistically update onSucess not onMutation?
Recommended approach to type-narrowing `useMutationState`?
useMutationState. From what I can tell, query uses a wide type because it's pretty difficult to infer the actual mutation state type based on the options for useMutationState, which is understandable.
What's the recommended approach in this case? Do manual narrowing in the predicate or select options?...Error handling with `queryClient.fetchQuery`
useQuery that used to manage fetching events that occur between two dates. The previous implementation expected external state, so this was no problem before. However, we are migrating to a different library, and it has a very different structure.
It instead expects me to handle (start: Date, end: Date, onSuccess: (events: ...[]) => void.
Most of the query hook is easily transferable to queryClient.fetchQuery (select, success handling, endpoint etc.). However, One thing I lose out on is the query.isError functionality, which is kind of a shame, because I know that this query can fail due to reasons that the user should know about.
...Pass a generic infiniteQueryOptions object as parameter
API call extremely slow in production but works fine in development