create-feltkit 0.3.3 → 0.3.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-feltkit",
-  "version": "0.3.3",
+  "version": "0.3.5",
   "description": "Create a FeltKit application: npm create feltkit@latest my-app (add -- --template managed for Managed FeltDB)",
   "license": "MIT",
   "type": "module",

package/template/README.md

@@ -163,6 +163,7 @@ FeltKit doesn't host your app; it builds what you run, for the way you want to r
 | `container` (default) | Everything in one container | FeltDB state on a volume |
 | `hosted` | A separate app container | Managed FeltDB, hosted for you, from the artifact's contract (it declares AppPort Services' collections too) |
 | `self-hosted` | A separate app container | A FeltDB server you operate (`feltdb-server`), in this app's namespace |
+| `vercel` | Vercel's container runtime (beta), scaling with traffic | Managed FeltDB, or your FeltDB server with `--data self-hosted` |
 
 Each target's `DEPLOY.md` spells out its contract: what to set, where state lives and how to
 recover it, what stops startup, and how to upgrade and roll back. A target never changes where
@@ -175,7 +176,7 @@ without their FeltDB settings.
    npx feltkit readiness --env production
    ```
 
-2. **Build and verify.** It asks which target (or pass `--target container`, `hosted` or `self-hosted`):
+2. **Build and verify.** It asks which target (or pass `--target container`, `hosted`, `self-hosted` or `vercel`):
 
    ```bash
    npm run deploy
@@ -213,7 +214,9 @@ without their FeltDB settings.
    `.feltkit/deploy/.env`, then run the same `docker compose` command. With your own FeltDB
    server (`--target self-hosted`), create a key for the app's namespace (`feltdb-server keys
    create --keys <keys.json> --name tasks --namespace tasks --scope state:read,state:write`) and
-   put `FELTDB_URL` and `FELTDB_TOKEN` in `.env`. Either container refuses to start without its
+   put `FELTDB_URL` and `FELTDB_TOKEN` in `.env`. On Vercel (`--target vercel`), follow
+   `.feltkit/deploy/DEPLOY.md`: `npx vercel link`, `npx vercel env add …` for each variable, then
+   `npx vercel deploy --prod`, all in `.feltkit/deploy`. Either container refuses to start without its
    settings, and checks the database answers, so it never keeps data on its own disk. For
    Fly.io, plain Docker, or other hosts, follow `.feltkit/deploy/DEPLOY.md`.
 

package/template/package.json

@@ -13,7 +13,7 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@feltdb/feltkit": "0.3.3",
+    "@feltdb/feltkit": "0.3.5",
     "react": "19.2.0",
     "react-dom": "19.2.0"
   },

package/template-managed/package.json

@@ -20,7 +20,7 @@
     "deploy:fly": "node scripts/deploy-fly.mjs"
   },
   "dependencies": {
-    "@feltdb/feltkit": "0.3.3"
+    "@feltdb/feltkit": "0.3.5"
   },
   "devDependencies": {
     "@feltdb/core": "0.16.1",