@nkzw/fate-indexeddb 1.12.2 → 1.14.0

package/README.md

@@ -1,11 +1,8 @@
 <!-- auto-generated from docs/guide/*.md and docs/integrations/*.md. Do not edit directly. -->
 
 <p align="center">
-  <picture>
-    <source media="(prefers-color-scheme: dark)" srcset="/public/fate-logo-dark.svg">
-    <source media="(prefers-color-scheme: light)" srcset="/public/fate-logo.svg">
-    <img alt="Logo" src="/public/fate-logo.svg" width="50%">
-  </picture>
+  <img alt="fate" src="/public/fate-logo.svg#gh-light-mode-only" width="50%">
+  <img alt="fate" src="/public/fate-logo-dark.svg#gh-dark-mode-only" width="50%">
 </p>
 
 **_fate_** is a modern data client for the web inspired by [Relay](https://relay.dev/) and [GraphQL](https://graphql.org/). It combines view composition, normalized caching, data masking, Async React features, and type-safe data fetching.
@@ -141,11 +138,8 @@ In fate, each component declares the data it needs using views. Views are compos
 Traditionally, React apps are built with components and hooks. fate introduces a third primitive: views – a declarative way for components to express their data requirements. An app built with fate looks more like this:
 
 <p align="center">
-  <picture class="fate-tree">
-    <source media="(prefers-color-scheme: dark)" srcset="/public/fate-tree-dark.svg">
-    <source media="(prefers-color-scheme: light)" srcset="/public/fate-tree.svg">
-    <img alt="Tree" src="/public/fate-tree.svg" width="90%">
-  </picture>
+  <img alt="Tree" src="/public/fate-tree.svg#gh-light-mode-only" width="90%">
+  <img alt="Tree" src="/public/fate-tree-dark.svg#gh-dark-mode-only" width="90%">
 </p>
 
 With fate, you no longer worry about _when_ to fetch data, how to coordinate loading states, or how to handle errors imperatively. You avoid overfetching, stop passing unnecessary data down the tree, and eliminate boilerplate types created solely for passing server data to child components.
@@ -874,6 +868,8 @@ function PostComments({
 
 `useView` and `useLiveListView` can read deferred values too. This works with every transport. GraphQL currently fetches deferred fields with separate queries, rather than streaming `@defer` responses.
 
+For GraphQL servers with incremental delivery enabled, [streaming batched reads](/docs/integrations/graphql.md#streaming-batched-reads) allows deferred follow-up requests to resolve independently within one HTTP response. This does not change when a deferred field is read or require different React hooks.
+
 ## List Views
 
 ### Pagination with `useListView`
@@ -2221,6 +2217,25 @@ Queries made together are batched into one GraphQL operation. Mutations run sepa
 
 [Deferred fields](/docs/guide/deferred-views.md) load when a component reads them. This uses ordinary GraphQL queries; incremental `@defer` responses are not supported yet.
 
+### Streaming Batched Reads
+
+For a server that supports GraphQL `@defer` and the `v0.2` incremental delivery protocol, enable streaming when creating your client:
+
+```tsx
+const fate = createFateClient({
+  streaming: true,
+  url: 'https://api.example.com/graphql',
+});
+```
+
+Reads still share one HTTP request. Each read is wrapped in its own labeled `@defer` fragment and resolves when that operation's complete result arrives. Separate requests under separate Suspense boundaries can render independently, while one request continues to wait for all the data it declares.
+
+The transport negotiates `multipart/mixed;incrementalSpec=v0.2` and also accepts complete JSON responses. Mutations continue to use ordinary JSON responses. Streaming is disabled by default; enable it only after configuring your server and verifying that your proxy forwards response chunks promptly. Unsupported directives and incompatible multipart protocols produce errors rather than silently retrying requests.
+
+With GraphQL Yoga, install `@graphql-yoga/plugin-defer-stream` and add `useDeferStream()` to the server's plugins. Keep client timeouts and error boundaries in place: completed reads remain available if another operation fails or the connection ends, while unfinished reads reject. Canceling one read keeps the connection alive for its siblings; the connection is released when no reads still need it.
+
+This mode delivers complete operation results through the existing normalized cache. Field-level patches and item-by-item `@stream` updates are not supported. Existing fate `defer()` selections remain lazy identity-based follow-up reads, which can themselves share a streaming batch.
+
 ### Refetch Fields
 
 For servers without `nodes(ids:)`, configure a query field for each refetchable entity type:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nkzw/fate-indexeddb",
-  "version": "1.12.2",
+  "version": "1.14.0",
   "description": "Optional IndexedDB persistence adapter for fate.",
   "license": "MIT",
   "files": [
@@ -19,10 +19,10 @@
     "idb": "^8.0.4"
   },
   "devDependencies": {
-    "@nkzw/fate": "1.12.2",
-    "fake-indexeddb": "^6.2.6",
-    "vite": "npm:@voidzero-dev/vite-plus-core@1.4.0",
-    "vite-plus": "1.4.0"
+    "@nkzw/fate": "1.14.0",
+    "fake-indexeddb": "^6.2.7",
+    "vite": "npm:@voidzero-dev/vite-plus-core@1.5.0",
+    "vite-plus": "1.5.0"
   },
   "peerDependencies": {
     "@nkzw/fate": "^1.5.1"