Safari has a known issue where overflow: hidden with border-radius
doesn't work correctly without hardware acceleration. Adding
transform: translateZ(0) forces GPU compositing which fixes the
icon rendering issue.
Fixes#10633
* docs(svelte): replace deprecated isLoading with isPending in overview
`isLoading` is a deprecated alias for `isPending && isFetching` and is
scheduled for removal in the next major version. The overview example
shows a standard (always-enabled) query, so `isPending` is the correct
flag. All other framework overview docs (React, Vue, Angular, Lit,
Preact) already use `isPending`.
Note: `isLoading` is intentionally retained in disabling-queries guides
where it is the right flag for disabled/lazy queries.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs(preact): add missing polling guide
The Polling guide existed for React, Vue, Solid, and Angular but was
missing from the Preact docs. Added the ref stub and wired it into
the nav config between Window Focus Refetching and Disabling Queries,
matching the ordering used by all other frameworks.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
`isLoading` is a deprecated alias for `isPending && isFetching` and is
scheduled for removal in the next major version. The overview example
shows a standard (always-enabled) query, so `isPending` is the correct
flag. All other framework overview docs (React, Vue, Angular, Lit,
Preact) already use `isPending`.
Note: `isLoading` is intentionally retained in disabling-queries guides
where it is the right flag for disabled/lazy queries.
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Inlining a `select` on a query object passed to `useQueries` /
`useSuspenseQueries` can't infer its `data` argument from the sibling
`queryFn` and falls back to `unknown` — a known TypeScript limitation
(TanStack/query#6556).
Document the two workarounds (annotate the `select` parameter, or define
the query with the `queryOptions` helper) in the React docs, and add type
tests guarding the behavior. Scoped to React for an easier review; the
other framework adapters can follow the same pattern in separate PRs.
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Under TypeScript 5.4, `NoInfer<T>` can't match an inline object literal
against the value branch of the `Updater` union in `setQueryData`, so it
falls back to the function branch and reports the literal as excess
properties (TS2353). TS >= 5.5 handles it correctly.
This surfaces in the `test:types:ts54` legacy typecheck via the project
reference chain (e.g. react-query-persist-client / react-query-devtools
build query-core's test sources). It is normally masked by the Nx remote
cache and only re-runs — and fails — when a dependent package's type
inputs change, so it can land on `main` unnoticed.
Annotate the value before passing it to `setQueryData` to sidestep the
5.4 limitation while preserving the assertions. Verified across TS
5.4–6.0.
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
* fix(hydration): set dataUpdatedAt when pending query resolves before hydration
* test(hydration): add cases for dataUpdatedAt when streamed query resolves before hydration
* Add changeset
---------
Co-authored-by: Fredrik Höglund <fredrik.hoglund@gmail.com>
* test(*): move 'vi.useRealTimers' to the end of 'afterEach' so cleanup runs under fake timers
* test(*): move 'vi.useRealTimers' to the end of 'afterEach' in persist-client and devtools suites
* test(svelte-query/createQueries): move 'vi.useRealTimers' to the end of 'afterEach'