shiply-cli 0.25.1 → 0.25.2

package/dist/index.js

@@ -409,11 +409,26 @@ async function main() {
                         anonymous: res.anonymous,
                         expiresAt: res.expiresAt,
                         updated: updating,
+                        ...(res.function ? { function: res.function } : {}),
                     })}\n`);
                     return;
                 }
                 const skipped = res.skipped > 0 ? ` (${res.skipped} unchanged, skipped)` : '';
                 console.log(`✔ ${updating ? `updated ${res.slug} in place` : 'published'} — ${res.uploaded} file${res.uploaded === 1 ? '' : 's'}${skipped}`);
+                // A failed function/bundle deploy does NOT fail the publish (static
+                // files still went live) — but a worker-backed site is broken without
+                // its worker, so surface the server's errors instead of swallowing them.
+                if (res.function?.errors?.length) {
+                    console.error(`\n✖ function deploy FAILED — the site's worker is NOT live:`);
+                    for (const err of res.function.errors)
+                        console.error(`    ${err}`);
+                }
+                else if (res.function?.deployed) {
+                    const crons = res.function.cronCount ? ` (${res.function.cronCount} cron${res.function.cronCount === 1 ? '' : 's'})` : '';
+                    console.log(`  function deployed${crons}`);
+                }
+                for (const hint of res.function?.hints ?? [])
+                    console.log(`    ${hint}`);
                 console.log(`\n  ${res.siteUrl}\n`);
                 // confirm the site actually serves, then celebrate
                 try {

package/dist/publish.js

@@ -52,8 +52,8 @@ export async function fetchWithRetry(url, init, opts = {}) {
     }
     throw new Error(`request to ${label} failed after ${attempts} attempts: ${lastErr?.message ?? 'unknown error'}`);
 }
-export async function api(url, init) {
-    const res = await fetchWithRetry(url, init, { label: `${init.method ?? 'GET'} ${url}` });
+export async function api(url, init, opts = {}) {
+    const res = await fetchWithRetry(url, init, { label: `${init.method ?? 'GET'} ${url}`, ...opts });
     const body = await res.json().catch(() => ({}));
     if (!res.ok) {
         const err = body.error;
@@ -87,12 +87,29 @@ export async function publish(dir, opts = {}) {
         }),
     });
     await uploadAll(dir, created.upload.uploads);
-    await api(created.upload.finalizeUrl, {
-        method: 'POST',
-        headers: { 'content-type': 'application/json' },
-        body: JSON.stringify({ versionId: created.upload.versionId }),
-    });
+    // Finalize deploys any worker bundle server-side, which can exceed the
+    // default 60s timeout — an aborted-then-retried finalize used to fail the
+    // whole publish with "already finalized" even though the deploy succeeded.
+    // Give it room, and treat that conflict as the success it is (an earlier
+    // attempt completed after the client gave up on it).
+    let finalized;
+    try {
+        finalized = await api(created.upload.finalizeUrl, {
+            method: 'POST',
+            headers: { 'content-type': 'application/json' },
+            body: JSON.stringify({ versionId: created.upload.versionId }),
+        }, { timeoutMs: 300_000 });
+    }
+    catch (e) {
+        if (e instanceof ApiError && e.code === 'conflict' && /already finalized/.test(e.message)) {
+            finalized = {}; // deployed by the earlier attempt; function info unavailable
+        }
+        else {
+            throw e;
+        }
+    }
     return {
+        ...(finalized.function ? { function: finalized.function } : {}),
         siteId: created.siteId,
         slug: created.slug,
         siteUrl: created.siteUrl,

package/dist/ssr-adapters.js

@@ -77,12 +77,13 @@ export async function detectSsr(dir) {
             // (esbuild shims it). The wrangler path applies asset-first in its own entry.
             bundleWith: 'wrangler',
             compatibilityFlags: ['nodejs_compat', 'global_fetch_strictly_public'],
-            // OpenNext imports `node:http`, which `nodejs_compat` only provides at a
-            // compat date >= ~2025-09 (verified: 2025-03-25 fails "No such module
-            // node:http", 2025-09-01 succeeds). OpenNext's own config bakes an older
-            // date that passes `wrangler --dry-run` (which doesn't validate runtime
-            // modules) but fails the real Workers upload — so we override it here.
-            compatibilityDate: '2025-09-01',
+            // OpenNext needs a modern compat date for its node:* imports: 2025-03-25
+            // fails "No such module node:http"; @opennextjs/cloudflare 1.20.x also
+            // imports `node:fs`, which 2025-09-01 still lacks (real upload fails —
+            // wrangler --dry-run doesn't validate runtime modules, and OpenNext's own
+            // config bakes an even older date). 2026-06-01 verified live with a
+            // Next 15 + OpenNext 1.20 deploy — so we override it here.
+            compatibilityDate: '2026-06-01',
         };
     }
     // Generic Cloudflare Worker via a wrangler config (Hono, itty, raw fetch).

package/package.json

@@ -1,42 +1,42 @@
-{
-  "name": "shiply-cli",
-  "version": "0.25.1",
-  "description": "Publish static sites to shiply.now from the command line — instant web hosting for agents.",
-  "license": "MIT",
-  "type": "module",
-  "bin": {
-    "shiply": "dist/index.js"
-  },
-  "files": [
-    "dist",
-    "skill",
-    "README.md"
-  ],
-  "scripts": {
-    "build": "tsc -p tsconfig.build.json",
-    "prepublishOnly": "pnpm build",
-    "test": "vitest run",
-    "typecheck": "tsc --noEmit"
-  },
-  "engines": {
-    "node": ">=18"
-  },
-  "keywords": [
-    "shiply",
-    "hosting",
-    "static",
-    "deploy",
-    "agents",
-    "publish"
-  ],
-  "homepage": "https://shiply.now",
-  "devDependencies": {
-    "@types/node": "^22.15.0",
-    "typescript": "^5.8.0",
-    "vitest": "^3.1.0"
-  },
-  "dependencies": {
-    "esbuild": "^0.25.12",
-    "smol-toml": "^1.7.0"
-  }
-}
+{
+  "name": "shiply-cli",
+  "version": "0.25.2",
+  "description": "Publish static sites to shiply.now from the command line \u00e2\u20ac\u201d instant web hosting for agents.",
+  "license": "MIT",
+  "type": "module",
+  "bin": {
+    "shiply": "dist/index.js"
+  },
+  "files": [
+    "dist",
+    "skill",
+    "README.md"
+  ],
+  "scripts": {
+    "build": "tsc -p tsconfig.build.json",
+    "prepublishOnly": "pnpm build",
+    "test": "vitest run",
+    "typecheck": "tsc --noEmit"
+  },
+  "engines": {
+    "node": ">=18"
+  },
+  "keywords": [
+    "shiply",
+    "hosting",
+    "static",
+    "deploy",
+    "agents",
+    "publish"
+  ],
+  "homepage": "https://shiply.now",
+  "devDependencies": {
+    "@types/node": "^22.15.0",
+    "typescript": "^5.8.0",
+    "vitest": "^3.1.0"
+  },
+  "dependencies": {
+    "esbuild": "^0.25.12",
+    "smol-toml": "^1.7.0"
+  }
+}

package/skill/CHANGELOG.md

@@ -6,6 +6,21 @@ entry here, that capability may be missing from your copy — re-install with
 (This is the agent-facing capability log; the CLI's own release notes live in
 the npm package changelog.)
 
+## 2026-07-07
+
+- **Fix** — custom domains attached to SSR/function sites no longer 404: the
+  platform's per-site access gate resolved requests by the wrong hostname on
+  custom-domain dispatch. No action needed; already-deployed sites are fixed
+  server-side, and the next publish bakes in the hardened gate.
+- **Fix** — `shiply publish` now surfaces server-side function/bundle deploy
+  errors and hints (previously discarded — a broken worker deploy looked like
+  a successful publish). Also included in `--json` output as `function`.
+- **Fix** — Next.js (OpenNext) deploys use compatibility date `2026-06-01`
+  (@opennextjs/cloudflare 1.20.x imports `node:fs`; the old date failed the
+  Workers upload with "No such module node:fs").
+- **Fix** — long finalize calls (large worker bundles) no longer abort at 60s
+  and mis-report a successful deploy as "already finalized".
+
 ## 2026-07-04
 
 - **Update** — the site-relative endpoints (`POST /.shiply/data/<collection>`,