* fix: update react and nextJs
and add a nextJs16 integration test
* ci: apply automated fixes
* oops
* Update patch versions for React and TanStack packages
Updated the patch versions for various React and TanStack packages.
* fix: streamline dependencies
* bundle size
* fix lock file
* fix: update react in example
* skip test for now
---------
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
* docs(vue): change query keys example to typescript
This example is written in Javascript, and the fact that `todoId` is a `Ref` is a bit hard to identify.
I propose to migrate this example to Typescript, with an import to Vue's Ref type and make the parameter to the example composable explicit.
There are more docs that could be improved this way, if it suits you I could also make the changes to these docs :)
* ci: apply automated fixes
---------
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
* fix(streamedQuery): fall back to initialValue when stream yields no values
Add failing test for empty streams and update implementation to avoid returning undefined.
Includes changeset for patch release.
* chore: address review nitpicks (JSDoc + test cleanup)
* docs: note that initialValue is returned when the stream yields no values
---------
Co-authored-by: Dominik Dorfmeister <office@dorfmeister.cc>
* fix(types): do not drop readonly for partial QueryFilter matching
* fix(types): allow QueryFilters union with different lengths
* Create orange-boxes-visit.md
* Apply suggestion from @TkDodo
* fix(query-core): allow partial query keys in `QueryFilters` and `MutationFilters`
Add a type to match tuple prefixes to match partial query keys in `QueryFilters` and `MutationFilters`
Fixestanstack/query#9680
* test(query-core): add tests for partial QueryKey matching for `QueryFilters`
add tests to verify that the new partial QueryKey matching for `QueryFilters` does match partial query keys, and also doesn't allow invalid query keys.
* fix(query-core): move tuple prefix helper types to utils.ts
prevent tuple helper types from getting exported, and showing up in the public api
* Add changeset
* ci: apply automated fixes
---------
Co-authored-by: Lachlan Collins <1667261+lachlancollins@users.noreply.github.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
* add community resources page
* update link for blog posts
* update community resource links
* rm vue community section
* update old links
* fix community resource link
* fix(core): only attach .then and .catch onto a promise if it gets dehydrated
* Fix promise handling in core for dehydrated states
Ensure .then and .catch are only attached to dehydrated promises.
docs: improve skipToken and refetch incompatibility warning
- Add detailed explanation of Missing queryFn error when using refetch() with skipToken
- Provide clear guidance to use enabled: false instead for manual refetching
- Systematic fix affects all frameworks (Vue, Angular, Solid) via inheritance
Fixes#7599
Fixes#9654
Solid Query documentation incorrectly shows useSuspenseQuery which doesn't exist in Solid Query. Added replacement rules to convert useSuspenseQuery to useQuery and useSuspenseQueries to useQueries.
This aligns the documentation with the actual Solid Query API.
Co-authored-by: MKM Lab <mkmlab@example.com>
* docs(solid-query): fix incorrect Vue.js code example in Suspense guide
Replace Vue.js code example with proper SolidJS syntax in the Suspense documentation.
The example was using Vue's defineComponent and setup() instead of SolidJS patterns.
Fixes issue with non-existent useSuspenseQuery examples in Solid Query docs.
* fix: use idiomatic SolidJS pattern for Suspense
Remove unnecessary createEffect and rely on direct query.data access.
According to TanStack Query Solid docs, accessing query.data directly
inside a Suspense boundary automatically triggers suspension.
Addresses CodeRabbit AI feedback for proper SolidJS patterns.
docs(angular): add missing replace rules for background-fetching-indicators
- Add replace rules to convert React terminology to Angular equivalents
- Fixes useIsFetching -> injectIsFetching conversion in prose text
- Adds hook -> function terminology conversion
- Includes package name conversion for @tanstack/react-query
- Resolves Issue #9744