@nkzw/fate-indexeddb 1.13.0 → 1.14.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +4 -10
  2. package/package.json +5 -5
package/README.md CHANGED
@@ -1,11 +1,8 @@
1
1
  <!-- auto-generated from docs/guide/*.md and docs/integrations/*.md. Do not edit directly. -->
2
2
 
3
3
  <p align="center">
4
- <picture>
5
- <source media="(prefers-color-scheme: dark)" srcset="/public/fate-logo-dark.svg">
6
- <source media="(prefers-color-scheme: light)" srcset="/public/fate-logo.svg">
7
- <img alt="Logo" src="/public/fate-logo.svg" width="50%">
8
- </picture>
4
+ <img alt="fate" src="/public/fate-logo.svg#gh-light-mode-only" width="50%">
5
+ <img alt="fate" src="/public/fate-logo-dark.svg#gh-dark-mode-only" width="50%">
9
6
  </p>
10
7
 
11
8
  **_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
141
138
  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:
142
139
 
143
140
  <p align="center">
144
- <picture class="fate-tree">
145
- <source media="(prefers-color-scheme: dark)" srcset="/public/fate-tree-dark.svg">
146
- <source media="(prefers-color-scheme: light)" srcset="/public/fate-tree.svg">
147
- <img alt="Tree" src="/public/fate-tree.svg" width="90%">
148
- </picture>
141
+ <img alt="Tree" src="/public/fate-tree.svg#gh-light-mode-only" width="90%">
142
+ <img alt="Tree" src="/public/fate-tree-dark.svg#gh-dark-mode-only" width="90%">
149
143
  </p>
150
144
 
151
145
  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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nkzw/fate-indexeddb",
3
- "version": "1.13.0",
3
+ "version": "1.14.1",
4
4
  "description": "Optional IndexedDB persistence adapter for fate.",
5
5
  "license": "MIT",
6
6
  "files": [
@@ -19,10 +19,10 @@
19
19
  "idb": "^8.0.4"
20
20
  },
21
21
  "devDependencies": {
22
- "@nkzw/fate": "1.13.0",
23
- "fake-indexeddb": "^6.2.6",
24
- "vite": "npm:@voidzero-dev/vite-plus-core@1.4.0",
25
- "vite-plus": "1.4.0"
22
+ "@nkzw/fate": "1.14.1",
23
+ "fake-indexeddb": "^6.2.7",
24
+ "vite": "npm:@voidzero-dev/vite-plus-core@1.5.0",
25
+ "vite-plus": "1.5.0"
26
26
  },
27
27
  "peerDependencies": {
28
28
  "@nkzw/fate": "^1.5.1"