Merge branch 'main' into rc

# Conflicts:
#	docs/react/devtools.md
#	packages/vue-query/package.json
#	packages/vue-query/src/useBaseQuery.ts

Author: TkDodo

CONTRIBUTING.md

@@ -82,7 +82,7 @@ Must be one of the following:
 - **fix**: A bug fix
 - **docs**: Documentation only changes
 - **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing
-  semi-colons, etc)
+  semicolons, etc.)
 - **refactor**: A code change that neither fixes a bug nor adds a feature
 - **perf**: A code change that improves performance
 - **test**: Adding missing or correcting existing tests

docs/react/guides/does-this-replace-client-state.md

@@ -12,7 +12,7 @@ With those points in mind, the short answer is that TanStack Query **replaces th
 
 For a vast majority of applications, the truly **globally accessible client state** that is left over after migrating all of your async code to TanStack Query is usually very tiny.
 
-> There are still some circumstances where an application might indeed have a massive amount of synchronous client-only state (like a visual designer or music production application), in which case, you will probably still want a client state manager. In this situation it's important to note that **TanStack Query is not a replacement for local/client state management**. However, you can use TanStack Query along side most client state managers with zero issues.
+> There are still some circumstances where an application might indeed have a massive amount of synchronous client-only state (like a visual designer or music production application), in which case, you will probably still want a client state manager. In this situation it's important to note that **TanStack Query is not a replacement for local/client state management**. However, you can use TanStack Query alongside most client state managers with zero issues.
 
 ## A Contrived Example
 
@@ -38,7 +38,7 @@ const globalState = {
 }
 ```
 
-This also means that with a few hook calls to `useQuery` and `useMutation`, we also get to remove any boilerplate code that was used to manage our server state eg.
+This also means that with a few hook calls to `useQuery` and `useMutation`, we also get to remove any boilerplate code that was used to manage our server state e.g.
 
 - Connectors
 - Action Creators

packages/vue-query/src/useBaseQuery.ts

@@ -25,9 +25,13 @@ export type UseBaseQueryReturnType<
   TError,
   Result = QueryObserverResult<TData, TError>,
 > = {
-  [K in keyof Result]: Result[K] extends (...args: Array<any>) => any
+  [K in keyof Result]: K extends
+    | 'fetchNextPage'
+    | 'fetchPreviousPage'
+    | 'refetch'
+    | 'remove'
     ? Result[K]
-    : ToRef<Result[K]>
+    : ToRef<Readonly<Result>[K]>
 } & {
   suspense: () => Promise<Result>
 }