@raf-query/react 0.7.4 → 0.7.6

package/CHANGELOG.md

@@ -1,8 +1,16 @@
 # Changelog
 
+## [0.7.6](https://github.com/KATT/raf-query/compare/0.7.5...0.7.6) (2026-10-14)
+
+* **agents:** open PRs ready for review unless experimental ([#99](https://github.com/KATT/raf-query/issues/99)) ([e141269](https://github.com/KATT/raf-query/commit/e141269cf290b56dcb452bb0aa63a3b490657142))
+
+## [0.7.5](https://github.com/KATT/raf-query/compare/0.7.4...0.7.5) (2026-10-14)
+
+- steer useIsFetching toward router pending and per-query isFetching ([#80](https://github.com/KATT/raf-query/issues/80)) ([c848b16](https://github.com/KATT/raf-query/commit/c848b162d31b1b16c8231d6f19be2420c12f5801))
+
 ## [0.7.4](https://github.com/KATT/raf-query/compare/0.7.3...0.7.4) (2026-10-14)
 
-* **agents:** verify with tests and preview links, and stack PRs for big work ([#93](https://github.com/KATT/raf-query/issues/93)) ([fbe282c](https://github.com/KATT/raf-query/commit/fbe282cc046abfa493afbfd147614dbeba878508))
+- **agents:** verify with tests and preview links, and stack PRs for big work ([#93](https://github.com/KATT/raf-query/issues/93)) ([fbe282c](https://github.com/KATT/raf-query/commit/fbe282cc046abfa493afbfd147614dbeba878508))
 
 ## [0.7.3](https://github.com/KATT/raf-query/compare/0.7.2...0.7.3) (2026-10-14)
 

package/dist/use-is-fetching.d.mts

@@ -2,9 +2,14 @@ import { QueryCache } from "@raf-query/core";
 //#region src/use-is-fetching.d.ts
 /**
  * How many queries have a request in flight: all of them, or those matching
- * `filter`. Re-renders when the count changes, for global loading
- * indicators. It's `0` on the server and while hydrating, so the server's
- * HTML and the browser's first render agree:
+ * `filter`. Re-renders when the count changes. It's `0` on the server and
+ * while hydrating, so the server's HTML and the browser's first render agree.
+ *
+ * You probably don't need this. Prefer the router's pending UI for
+ * navigations (`useRouterState` / `pendingComponent` in TanStack Router,
+ * `useLinkStatus` in Next.js) and per-query `controls.isFetching` for
+ * background refetches. Kept for TanStack Query compatibility when you want
+ * one global count of every in-flight request:
  *
  * ```tsx
  * const fetching = useIsFetching();

package/dist/use-is-fetching.mjs

@@ -16,9 +16,14 @@ function subscribeDeferred(client, onStoreChange) {
 const none = () => 0;
 /**
 * How many queries have a request in flight: all of them, or those matching
-* `filter`. Re-renders when the count changes, for global loading
-* indicators. It's `0` on the server and while hydrating, so the server's
-* HTML and the browser's first render agree:
+* `filter`. Re-renders when the count changes. It's `0` on the server and
+* while hydrating, so the server's HTML and the browser's first render agree.
+*
+* You probably don't need this. Prefer the router's pending UI for
+* navigations (`useRouterState` / `pendingComponent` in TanStack Router,
+* `useLinkStatus` in Next.js) and per-query `controls.isFetching` for
+* background refetches. Kept for TanStack Query compatibility when you want
+* one global count of every in-flight request:
 *
 * ```tsx
 * const fetching = useIsFetching();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@raf-query/react",
-  "version": "0.7.4",
+  "version": "0.7.6",
   "description": "React bindings for raf-query, a render-as-you-fetch query library",
   "keywords": [
     "query",
@@ -46,7 +46,7 @@
     }
   },
   "dependencies": {
-    "@raf-query/core": "0.7.4"
+    "@raf-query/core": "0.7.6"
   },
   "peerDependencies": {
     "@tanstack/react-router": "^1.170.0",