create-feltkit 0.3.7 → 0.3.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-feltkit",
-  "version": "0.3.7",
+  "version": "0.3.8",
   "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

@@ -219,7 +219,8 @@ without their FeltDB settings.
    --runtime-scopes minimal`, which writes `.env.local`), then run `npx feltkit vercel deploy`. It links
    the Vercel project the first time, uploads only the settings the deployment needs, deploys, and
    signs you in: it prints the app's URL, your session token, and a one-time link to production
-   Studio. Either container refuses to start without its
+   Studio. On Cloudflare (`--target cloudflare`), the same with `npx feltkit cloudflare deploy`
+   (Docker must be running: wrangler builds the image locally). 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.7",
+    "@feltdb/feltkit": "0.3.8",
     "react": "19.2.0",
     "react-dom": "19.2.0"
   },
@@ -24,10 +24,5 @@
     "@vitejs/plugin-react": "5.1.0",
     "typescript": "5.9.3",
     "vite": "7.3.7"
-  },
-  "overrides": {
-    "@appport/services": {
-      "@feltdb/core": "0.16.1"
-    }
   }
 }

package/template-managed/package.json

@@ -20,16 +20,11 @@
     "deploy:fly": "node scripts/deploy-fly.mjs"
   },
   "dependencies": {
-    "@feltdb/feltkit": "0.3.7"
+    "@feltdb/feltkit": "0.3.8"
   },
   "devDependencies": {
     "@feltdb/core": "0.16.1",
     "@types/node": "22.19.1",
     "typescript": "5.9.3"
-  },
-  "overrides": {
-    "@appport/services": {
-      "@feltdb/core": "0.16.1"
-    }
   }
 }