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.
Severe TypeScript Performance Degradation with `@tanstack/vue-query` in Vue 3 + TypeScript Project
### Describe the bug After installing and importing @tanstack/vue-query (and related packages), VSCode performance drops significantly in my Vue 3 + TypeScript project. The following editor features are noticeably slowed...
### Describe the bug When using the factory `queryOptions` and exporting the result, TypeScript errors appear: ``` Exported variable 'shopsQuery' has or is using name 'dataTagErrorSymbol' from external module "/node_modules/@tanstack/query-core/build/legacy/hydration-DiTAi-4H"...
## Partially fixes https://github.com/TanStack/query/issues/8639 ## TODOs: - We should try to push `NoInfer` upstream into the `query-core` types (eg. `QueryObserverResult`) - I didn't have extensive time, but didn't have any...
### Describe the bug Related to https://github.com/TanStack/query/issues/4770, revitalizing since `NoInfer`/overloads can at _least_ partially help. - `TQueryFnData` is directly inferred from `queryFn` specified in the hook options `options` - `TData`...
### Describe the bug The type of `context` in the `useMutation` callbacks depends on the sorting of the options object. ### Your minimal, reproducible example https://codesandbox.io/p/devbox/usemutationcontext-qsnk89 ### Steps to reproduce...
## 🎯 Changes Fixes https://github.com/TanStack/query/issues/9020 The issue was that the effect that subscribes to the observer runs after the observer emits the first state change if the mutation is triggered...
### Describe the bug When trying to include the Dev Tools in a TanStack Solid Start project, the button doesn't show up and we just get the text `[object Promise]`...
### Describe the bug ``` export default function Page() { const [n, setN] = useState(0); const queries = useQueries({ queries: [...Array(n).keys()].map((i) => ({ queryKey: [i], queryFn: () => i, })),...
Probably during the merge conflict resolution, some imports were not updated correctly. This commit fixes these imports in order to make all tests pass again.
I integrated util function "noop". The function "noop" is already made in "query-core" package. So, we don't need to make again in "react-query" package
