void-fate 1.5.2 → 1.6.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 +23 -4
  2. package/package.json +8 -8
package/README.md CHANGED
@@ -6,18 +6,20 @@ Void adapter for [fate](https://github.com/nkzw-tech/fate).
6
6
  client wrapper needed to use fate in a Void app without keeping adapter glue in
7
7
  application code.
8
8
 
9
+ Deploy the same app to your own Cloudflare account or the Void platform.
10
+
9
11
  ## New Project
10
12
 
11
13
  For a new Void app, start from the Void template:
12
14
 
13
15
  ```sh
14
- vp create fate my-app --template void
16
+ vp create fate -- --template void
15
17
  ```
16
18
 
17
19
  Use Vue instead of React with:
18
20
 
19
21
  ```sh
20
- vp create fate my-app --template void --framework vue
22
+ vp create fate -- --template void --framework vue
21
23
  ```
22
24
 
23
25
  ## Existing Project
@@ -25,9 +27,26 @@ vp create fate my-app --template void --framework vue
25
27
  For an existing Void project, add the packages directly:
26
28
 
27
29
  ```sh
28
- pnpm add @nkzw/fate react-fate void-fate void
30
+ pnpm add @nkzw/fate react-fate void-fate void @void/react
31
+ ```
32
+
33
+ ## Cloudflare Deployment
34
+
35
+ From the project root:
36
+
37
+ ```sh
38
+ vp exec void deploy --platform cloudflare
29
39
  ```
30
40
 
41
+ The Void template includes the `VOID_LIVE` Durable Object binding and class migration.
42
+ Void provisions resources, applies checked-in database migrations, and deploys the app
43
+ directly to your Cloudflare account. Commit the resource IDs saved in `wrangler.jsonc`.
44
+
45
+ After changing your database schema or auth configuration, run `vp exec void db generate`
46
+ and review and commit the migrations before deploying. See the
47
+ [Cloudflare integration](https://fate.technology/integrations/cloudflare) for migration
48
+ instructions for existing apps.
49
+
31
50
  ## Vite
32
51
 
33
52
  Use the regular `react-fate` Vite plugin with the Void transport.
@@ -131,7 +150,7 @@ export default function Layout({
131
150
  ## Custom Paths
132
151
 
133
152
  The defaults are intended to work without configuration. If your Void routes use
134
- different paths, pass the same values to the server and client helpers.
153
+ different paths, update the route filenames and pass the matching paths to the client.
135
154
 
136
155
  ```tsx
137
156
  <VoidFateClient livePath="/custom-live" origin={origin} rpcPath="/custom-fate" userId={userId}>
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "void-fate",
3
- "version": "1.5.2",
3
+ "version": "1.6.1",
4
4
  "description": "Void adapter for fate.",
5
5
  "homepage": "https://github.com/nkzw-tech/fate",
6
6
  "license": "MIT",
@@ -37,20 +37,20 @@
37
37
  }
38
38
  },
39
39
  "dependencies": {
40
- "@nkzw/fate": "^1.5.1",
41
- "react-fate": "^1.5.1"
40
+ "@nkzw/fate": "1.6.1",
41
+ "react-fate": "1.6.1"
42
42
  },
43
43
  "devDependencies": {
44
- "@types/react": "^19.3.0",
45
- "react": "^19.3.0",
46
- "vite": "npm:@voidzero-dev/vite-plus-core@0.3.2",
47
- "void": "^0.10.13"
44
+ "@types/react": "19.3.0",
45
+ "react": "19.3.0",
46
+ "vite": "npm:@voidzero-dev/vite-plus-core@0.3.3",
47
+ "void": "^0.20.1"
48
48
  },
49
49
  "peerDependencies": {
50
50
  "@nkzw/fate": "^1.0.0-rc.0",
51
51
  "react": "^19.2.0",
52
52
  "react-fate": "^1.0.0-rc.0",
53
- "void": "^0.7.13"
53
+ "void": "^0.20.1"
54
54
  },
55
55
  "scripts": {
56
56
  "build": "vp pack --tsconfig tsconfig.json -d lib --target=node24 src/index.ts src/react.tsx src/server.ts"