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
setQueryData & nested arrays immutability
useQueries with retries and redirects end up using the same redirect for all Queries
Invalidate React Query on SSR Next JS (App Router)
Query/Mutations as nested record
useQuery
& others.
```
The inferred type of 'teacherSessionAPI' cannot be named without a reference to '.pnpm/@tanstack+query-core@5.80.7/node_modules/@tanstack/query-core/build/legacy/hydration-Cr-4Kky1'. This is likely not portable. A type annotation is necessary.ts(2742)...Using useQuery result in custom hook
useMutation in Context+Provider infinite calls
createContext
and provider to then be able to access it a bit deeper down easily, that'd be useful. I am completely unable to get this to work or understand why I am getting infinite re-renders. I have tried everything chat gippity is suggesting and have googled as much as possible....useMutation refreshing problem
Is select callback only meant for data transformation?
What causes `queryClient.invalidateQueries()` to error when all requests are good?
Is it possible to wait for a few seconds before invalidates the cache in onSuccess?
Can `useQuery`'s result type figure out that all errors throw?
throwOnError
is set, one only needs to eliminate pending
in order to guarantee this state of affairs. Is this a deliberate design decision, am I doing things wrongly, or is it some sort of inherent TypeScript limitation?Quick question about key equality and using it with gql
As long as the query key is serializable using JSON.stringifyDoes this mean they are checked via the JSON serialised version for equality? So if I did:...
with nextjs what is the best way to architect your queries?
SSE background Fetching while component unmount
Weird type bug when using `queryOptions` with `useQueries`
name
, the types of results
in the combine
function seems to be wrong. Any ideas on why this is?
```ts
import { queryOptions, useQueries } from "@tanstack/react-query";
...default mutation onError fallback?
Experimental streaming without prefetching in Next.js
@tanstack/react-query-next-experimental
and I understand that a new QueryClient
is created for each server request.
However, on a single frontend route, I have both the layout and the page, which are server-side, and they make the same request to the backend.
Is there any alternative where I can cache these requests within the same frontend route?...
Typescript DX assistance "request"?

Using useSuspenseQuery for paginated requests
useSuspenseQuery
is not the preferred way to render paginated data because, when changing pages, it is harder to show a loading state due to the existing data from the previous page? Or am I missing something?
I am changing pages through React Router search params from another component.
Currently, page changes work, but there is no indication of a loading state as there is with the initial useSuspenseQuery
fetching....Non-undefined placeholderData types as possibly undefined
placeholderData
function always returns a proper result (not undefined), then why is the resulting data
property typed as T | undefined
?
Consider the following example:
```typescript...