feat: initial v3 changes

Author: boschni

core/package.json

@@ -0,0 +1,6 @@
+{
+  "internal": true,
+  "main": "../lib/core/index.js",
+  "module": "../es/core/index.js",
+  "types": "../types/core/index.d.ts"
+}

docs/src/pages/docs/api.md

@@ -52,7 +52,7 @@ const {
 const queryInfo = useQuery({
   queryKey,
   queryFn,
-  config,
+  enabled,
 })
 ```
 
@@ -124,6 +124,9 @@ const queryInfo = useQuery({
 - `onSettled: Function(data, error) => data`
   - Optional
   - This function will fire any time the query is either successfully fetched or errors and be passed either the data or error
+- `select: (data) => data`
+  - Optional
+  - This option can be used to transform or select a part of the data returned by the query function.
 - `suspense: Boolean`
   - Optional
   - Set this to `true` to enable suspense mode.
@@ -186,7 +189,7 @@ const queryInfo = useQuery({
   - The failure count for the query.
   - Incremented every time the query fails.
   - Reset to `0` when the query succeeds.
-- `refetch: Function({ throwOnError }) => Promise<TResult | undefined>`
+- `refetch: Function({ throwOnError }) => Promise<TData | undefined>`
   - A function to manually refetch the query.
   - If the query errors, the error will only be logged. If you want an error to be thrown, pass the `throwOnError: true` option
 - `remove: Function() => void`
@@ -253,7 +256,7 @@ The returned properties for `useInfiniteQuery` are identical to the [`useQuery`
 
 - `isFetchingMore: false | 'next' | 'previous'`
   - If using `paginated` mode, this will be `true` when fetching more results using the `fetchMore` function.
-- `fetchMore: Function(fetchMoreVariableOverride) => Promise<TResult | undefined>`
+- `fetchMore: Function(fetchMoreVariableOverride) => Promise<TData | undefined>`
   - This function allows you to fetch the next "page" of results.
   - `fetchMoreVariableOverride` allows you to optionally override the fetch more variable returned from your `getFetchMore` option to your query function to retrieve the next page of results.
 - `canFetchMore: Boolean`
@@ -391,7 +394,7 @@ try {
 
 **Returns**
 
-- `Promise<TResult>`
+- `Promise<TData>`
 
 ## `queryCache.prefetchQuery`
 
@@ -436,7 +439,7 @@ The options for `prefetchQuery` are exactly the same as those of [`useQuery`](#u
 
 **Returns**
 
-- `Promise<TResult | undefined>`
+- `Promise<TData | undefined>`
   - A promise is returned that will either immediately resolve with the query's cached response data, or resolve to the data returned by the fetch function. It **will not** throw an error if the fetch fails. This can be configured by setting the `throwOnError` option to `true`.
 
 ## `queryCache.getQueryData`
@@ -837,16 +840,16 @@ function App() {
 - `queryCache: QueryCache`
   - Instance of QueryCache.
 
-## `ReactQueryErrorResetBoundary`
+## `QueryErrorResetBoundary`
 
-When using **suspense** or **useErrorBoundaries** in your queries, you need a way to let queries know that you want to try again when re-rendering after some error occured. With the `ReactQueryErrorResetBoundary` component you can reset any query errors within the boundaries of the component.
+When using **suspense** or **useErrorBoundaries** in your queries, you need a way to let queries know that you want to try again when re-rendering after some error occured. With the `QueryErrorResetBoundary` component you can reset any query errors within the boundaries of the component.
 
 ```js
-import { ReactQueryErrorResetBoundary } from 'react-query'
+import { QueryErrorResetBoundary } from 'react-query'
 import { ErrorBoundary } from 'react-error-boundary'
 
 const App: React.FC = () => (
-  <ReactQueryErrorResetBoundary>
+  <QueryErrorResetBoundary>
     {({ reset }) => (
       <ErrorBoundary
         onReset={reset}
@@ -860,20 +863,20 @@ const App: React.FC = () => (
         <Page />
       </ErrorBoundary>
     )}
-  </ReactQueryErrorResetBoundary>
+  </QueryErrorResetBoundary>
 )
 ```
 
-## `useErrorResetBoundary`
+## `useQueryErrorResetBoundary`
 
-This hook will reset any query errors within the closest `ReactQueryErrorResetBoundary`. If there is no boundary defined it will reset them globally:
+This hook will reset any query errors within the closest `QueryErrorResetBoundary`. If there is no boundary defined it will reset them globally:
 
 ```js
-import { useErrorResetBoundary } from 'react-query'
+import { useQueryErrorResetBoundary } from 'react-query'
 import { ErrorBoundary } from 'react-error-boundary'
 
 const App: React.FC = () => {
-  const { reset } = useErrorResetBoundary()
+  const { reset } = useQueryErrorResetBoundary()
   return (
     <ErrorBoundary
       onReset={reset}

docs/src/pages/docs/comparison.md

@@ -28,6 +28,7 @@ Feature/Capability Key:
 | Paginated Queries                            | ✅                                     | ✅                         | ✅                                    |
 | Infinite Queries                             | ✅                                     | ✅                         | ✅                                    |
 | Lagged / "Lazy" Queries<sup>1</sup>          | ✅                                     | 🛑                         | 🛑                                    |
+| Selectors                                    | ✅                                     | 🛑                         | ✅                                    |
 | Initial Data                                 | ✅                                     | ✅                         | ✅                                    |
 | Scroll Recovery                              | ✅                                     | ✅                         | ✅                                    |
 | Cache Manipulation                           | ✅                                     | ✅                         | ✅                                    |