@solcreek/cli 0.4.23 → 0.4.24

package/CHANGELOG.md

@@ -1,5 +1,35 @@
 # @solcreek/cli
 
+## 0.4.24
+
+### Fixes / DX
+
+- **`creek init --db` adds a database without prompting.** Non-interactive
+  runs (CI, coding agents) previously skipped the "Add a database?"
+  question silently and produced a config without one. With `--db`, init
+  writes `[resources] database = true` and `[build].worker`, and scaffolds
+  the worker/index.ts example. When the prompt is skipped, init now says
+  so and points at `--db` (`--json` output gets a `databasePromptSkipped`
+  field and a breadcrumb).
+
+- **`creek init <name>` sets the project name.** The positional name was
+  ignored and the directory basename used instead; `--name` was the only
+  working form.
+
+- **`creek doctor` catches the resources-without-worker mismatch.** Two new
+  findings: declaring resources with no worker entry (the deploy would be a
+  static SPA where `/api/*` serves index.html — warn), and a worker file on
+  disk that no config points at, so it would never deploy (info).
+
+- **`creek deploy` warns before shipping a static SPA that declares
+  resources**, naming the bindings and pointing at `[build].worker` — the
+  same mismatch doctor flags, surfaced even when doctor never ran.
+
+- **The "nothing to deploy" finding now presents both fixes.** Build output
+  and worker entry are separate inputs; the guidance previously steered
+  only toward re-running the build, leaving API-route projects chasing the
+  wrong one.
+
 ## 0.4.23
 
 ### Fixes / DX

package/dist/commands/doctor.js

@@ -169,7 +169,9 @@ function s(n) {
 // CK_FIX_HINTS). Keep all three in sync when adding a new CK-* rule.
 const CK_FIX_HINTS = {
     "CK-NO-CONFIG": "Run `creek init` to scaffold a creek.toml, or cd to a directory that contains creek.toml / wrangler.* / package.json / index.html.",
-    "CK-NOTHING-TO-DEPLOY": "Run the project's build command so there's output in [build].output, or set [build].command in creek.toml if the project needs one.",
+    "CK-NOTHING-TO-DEPLOY": "Run the project's build command so there's output in [build].output, or set [build].command in creek.toml if the project needs one. If the project has server code / API routes, also set [build].worker — the build alone never declares it.",
+    "CK-RESOURCES-NO-WORKER": "Resources are declared but no worker entry — the deploy is a static SPA and /api/* serves index.html. Set [build].worker in creek.toml (e.g. worker = \"worker/index.ts\"), or remove [resources] if the site is purely static.",
+    "CK-WORKER-UNDECLARED": "A worker-shaped file exists on disk but no worker entry is declared, so it will not be deployed. Point [build].worker in creek.toml at it, or delete the file if unused.",
     "CK-DB-DUAL-DRIVER-SPLIT": "Consolidate the split db.local.ts + db.prod.ts files. Share schema.ts and routes.ts; keep only thin boot files (server/local.ts for dev, server/worker.ts for prod) that differ in driver setup. See examples/vite-react-drizzle.",
     "CK-SYNC-SQLITE": "better-sqlite3 is synchronous and won't run on Workers. Migrate to an async ORM with a D1 adapter — Drizzle or Kysely are the drop-in paths.",
     "CK-PRISMA-SQLITE": "Prisma's SQLite datasource isn't supported on Cloudflare Workers. Switch to Drizzle or Kysely with a D1 adapter.",

package/dist/commands/init.d.ts

@@ -10,10 +10,15 @@ export declare const initCommand: import("citty").CommandDef<{
         default: boolean;
     };
     name: {
-        type: "string";
+        type: "positional";
         description: string;
         required: false;
     };
+    db: {
+        type: "boolean";
+        description: string;
+        default: false;
+    };
     adopt: {
         type: "string";
         description: string;

package/dist/commands/init.js

@@ -11,14 +11,19 @@ import { ensureGitignoreEntries } from "../utils/gitignore.js";
 export const initCommand = defineCommand({
     meta: {
         name: "init",
-        description: "Initialize a new Creek project — writes creek.toml (project name, build command/output, detected framework) and, if you add a database, a worker/index.ts example. Or register a self-host creekd via --adopt / --hostkey-fingerprint.",
+        description: "Initialize a new Creek project — writes creek.toml (project name, build command/output, detected framework) and, if you add a database (interactive prompt or --db), a worker/index.ts example. Or register a self-host creekd via --adopt / --hostkey-fingerprint.",
     },
     args: {
         name: {
-            type: "string",
+            type: "positional",
             description: "Project name (project init) OR host short-name (self-host init)",
             required: false,
         },
+        db: {
+            type: "boolean",
+            description: "Add a database without prompting — writes [resources] database = true and scaffolds worker/index.ts. Required to get the database path in non-interactive runs (the prompt is skipped there).",
+            default: false,
+        },
         adopt: {
             type: "string",
             description: "TOFU-pin a creekd host at <addr> (Path B). Fetches GET /v1/hostkey, prompts to verify, writes ~/.creek/hosts.json.",
@@ -62,10 +67,20 @@ export const initCommand = defineCommand({
         }
         const defaultName = basename(cwd).toLowerCase().replace(/[^a-z0-9-]/g, "-");
         const name = args.name ?? defaultName;
-        // Ask about database
-        let useDb = false;
-        if (!jsonMode && !shouldAutoConfirm(args)) {
-            useDb = await consola.prompt("Add a database?", { type: "confirm" });
+        // Ask about database. --db answers without prompting; otherwise the
+        // prompt only fires in interactive runs. In non-interactive runs
+        // (agents, CI — jsonMode or auto-confirm) the question is skipped,
+        // and we say so: silently defaulting to "no database" is how users
+        // end up hand-editing creek.toml and missing [build].worker.
+        let useDb = args.db === true;
+        let dbPromptSkipped = false;
+        if (!useDb) {
+            if (!jsonMode && !shouldAutoConfirm(args)) {
+                useDb = await consola.prompt("Add a database?", { type: "confirm" });
+            }
+            else {
+                dbPromptSkipped = true;
+            }
         }
         const config = {
             project: {
@@ -127,13 +142,19 @@ export default app;
             }
         }
         if (jsonMode) {
-            jsonOutput({ ok: true, name, framework: framework ?? null, database: useDb, path: configPath }, 0, [
+            jsonOutput({ ok: true, name, framework: framework ?? null, database: useDb, databasePromptSkipped: dbPromptSkipped, path: configPath }, 0, [
+                ...(dbPromptSkipped
+                    ? [{ command: "creek init --db", description: "Re-run with a database — writes [resources] and [build].worker, scaffolds worker/index.ts" }]
+                    : []),
                 { command: "creek deploy", description: "Deploy the project" },
                 { command: "creek dev", description: "Start local development server" },
             ]);
         }
         consola.success(`Created creek.toml for "${name}"`);
         if (!jsonMode) {
+            if (dbPromptSkipped) {
+                consola.info("Skipped the database prompt (non-interactive). Re-run with `creek init --db` to add one — it writes [resources] and [build].worker and scaffolds worker/index.ts.");
+            }
             console.log("");
             consola.info("  Next steps:");
             consola.info("    creek deploy    Deploy to production");
@@ -146,7 +167,7 @@ export default app;
  *
  * Two paths:
  *
- *   Path B: --adopt=<addr> [--name <name>]
+ *   Path B: --adopt=<addr> [<name>]
  *     Fetches GET /v1/hostkey, recomputes the fingerprint from the
  *     returned publicKey, prompts the operator to verify against
  *     the provider console / paper bundle, and writes the pinned
@@ -271,7 +292,7 @@ async function initHostAdopt(addr, pastedFingerprint, hostName, jsonMode, autoCo
  * Derive a short host name from the adopt address. e.g.
  *   --adopt=5.75.231.44:9080 → "h-5-75-231-44"
  *   --adopt=my.host.dev      → "h-my-host-dev"
- * Operator may override via --name.
+ * Operator may override via the positional name argument.
  */
 function defaultHostName(addr) {
     const noScheme = addr.replace(/^https?:\/\//, "").replace(/[:/].*$/, "");

package/dist/utils/prepare-bundle.js

@@ -245,6 +245,15 @@ export async function prepareDeployBundle(input) {
     const effectiveEntrypoint = astroAdapter
         ? "entry.mjs"
         : (plan.worker.entry ?? null);
+    // Resources declared but the deploy carries no server code: the
+    // bindings get provisioned with nothing able to read them, and
+    // /api/* serves static assets (unknown paths fall back to
+    // index.html). Same condition as doctor's CK-RESOURCES-NO-WORKER —
+    // repeated here because most deploys never run `creek doctor` first.
+    const resourceBindings = resolved.bindings.filter((b) => b.type === "d1" || b.type === "r2" || b.type === "kv" || b.type === "ai");
+    if (effectiveRenderMode === "spa" && resourceBindings.length > 0) {
+        consola.warn(`  Resources declared (${resourceBindings.map((b) => `env.${b.name}`).join(", ")}) but no worker entry — deploying as a static SPA. /api/* will serve index.html, not server code. If that's unintended, set [build].worker in creek.toml (details: creek doctor).`);
+    }
     return {
         plan,
         framework,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@solcreek/cli",
-  "version": "0.4.23",
+  "version": "0.4.24",
   "description": "CLI for the Creek deployment platform",
   "type": "module",
   "main": "./dist/index.js",
@@ -33,7 +33,7 @@
     "esbuild": "^0.25.0",
     "smol-toml": "^1.3.1",
     "ws": "^8.20.0",
-    "@solcreek/sdk": "0.4.11"
+    "@solcreek/sdk": "0.4.12"
   },
   "devDependencies": {
     "@testing-library/dom": "^10.4.1",