query
query copied to clipboard
TanStack
🤖 Powerful asynchronous state management, server-state utilities and data fetching for the web. TS/JS, React Query, Solid Query, Svelte Query and Vue Query.
### context With nextJs 13 also requiring React18, it makes sense to follow suit. All new features are build on top of react18. This means we can also drop the...
### context in v4, we introduced the possibility to pass a custom context to all react-query hooks. This allowed for proper isolation when using MicroFrontends. See [the migration guide](https://tanstack.com/query/v4/docs/guides/migrating-to-react-query-4#custom-contexts-for-multiple-providers) for...
### context The `QueryClientProvider` has a prop `contextSharing: boolean`. The docs say: > Set this to `true` to enable context sharing, which will share the first and at least one...
We have two props that go together on `useQuery` that are around [structural sharing](https://tkdodo.eu/blog/react-query-render-optimizations#structural-sharing): - `isDataEqual?: (oldData: TData | undefined, newData: TData) => boolean` - default: `undefined` - `structuralSharing?: boolean...
### context The "big" bundle size is a constant topic when TanStack Query is compared to other libraries. I think there are a few things that can be done to...
### context A property that starts with the prefix `use` is unfortunately named, as `use` usually indicates a hook in React. `ErrorBoundary` might also be a quite react specific term....
This pull request adds Svelte adapter for TanStack Query. Primitives included in the package are: - useQueryClient - useQuery - userQueries - useMutation - useInfiniteQuery - useHydrate - useIsMutating -...
### Describe the bug Lots of duplicate requests when scrolling too fast  ### Your minimal, reproducible example https://codesandbox.io/s/reverent-sanne-witpsy ### Steps to reproduce Select all the tables with the mouse...
If two roots shared the `QueryClient` instance, then it would never unsubscribe from online/focus manager listeners and would also forever receive duplicate events because the unsubscriber functions would get "forgotten"....
