@takazudo/zfb-adapter-cloudflare 0.1.0-next.96 → 0.1.0-next.97

package/README.md

@@ -70,7 +70,9 @@ lifecycle (`wrangler d1 create`, migrations, preview-vs-prod).
    `dist/`.
 2. Hand the SSR bundle to this adapter, which writes `dist/_worker.js`
    (the wrapper), `dist/_zfb_inner.mjs` (the bundle), copied
-   `x-<hash>.wasm` modules, and `dist/.assetsignore` (see below) — ready
+   `<name>-<hash>.wasm` modules (e.g. `index_bg-a1b2c3d4.wasm` — this is
+   esbuild's own `--asset-names=[name]-[hash]` convention, not a
+   zfb-specific scheme), and `dist/.assetsignore` (see below) — ready
    for Workers Static Assets.
 
 ## `wrangler.toml`

package/dist/worker-wrapper.mjs

@@ -48,8 +48,9 @@ export const WORKER_WRAPPER_SOURCE = `// AUTO-GENERATED by @takazudo/zfb-adapter
 //     \`pages/api/*.tsx\`) are served. EXCEPTION: when the asset 404
 //     carries a *styled* 404-page body (\`not_found_handling = "404-page"\`
 //     on Workers Static Assets, or the \`404.html\` convention on Pages —
-//     detected as an HTML document with a real Content-Length) AND the
-//     inner ALSO 404s with only the framework default body (Hono's
+//     detected as an HTML document by content-type; the assets binding
+//     streams every response and never sends a \`content-length\` header)
+//     AND the inner ALSO 404s with only the framework default body (Hono's
 //     default not-found, \`text/plain\` "404 Not Found", or a bare 404
 //     with no content-type), the earlier styled asset 404 is preferred
 //     over the inner's plain 404 — otherwise the styled \`404.html\` would
@@ -94,15 +95,17 @@ function assetHasStyled404Body(response) {
   // True iff an ASSETS 404 carries the site's *styled* 404 page.
   // Platform fact: \`not_found_handling = "404-page"\` (Workers Static
   // Assets) and the Pages \`404.html\` convention both serve that page as
-  // an HTML document — auto-detected \`content-type: text/html\` and a real
-  // \`Content-Length\` (it is a static file). \`not_found_handling = "none"\`
-  // and a bare Pages advanced-mode 404 send Cloudflare's default 404 with
-  // an empty / non-HTML body, so this returns false and the inner wins.
+  // an HTML document — auto-detected \`content-type: text/html\`. The
+  // Workers Static Assets binding streams every response (chunked
+  // locally, HTTP/2 framed in production) and never sends a
+  // \`content-length\` header, so content-type alone is the discriminator.
+  // \`not_found_handling = "none"\` sends Cloudflare's default 404 with
+  // NO headers at all (empty/non-HTML content-type), so this still
+  // returns false there and the inner wins.
   // Header-only (never reads the body) so it holds for HEAD too and leaves
   // the one-shot asset stream intact for a verbatim return.
   const contentType = (response.headers.get("content-type") || "").toLowerCase();
-  const contentLength = Number(response.headers.get("content-length") || "0");
-  return contentType.includes("text/html") && contentLength > 0;
+  return contentType.includes("text/html");
 }
 
 function innerIsFrameworkDefault404(response) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@takazudo/zfb-adapter-cloudflare",
-  "version": "0.1.0-next.96",
+  "version": "0.1.0-next.97",
   "private": false,
   "type": "module",
   "description": "Rust-built static-site engine for Astro and Next.js users — millisecond rebuilds, single binary. Cloudflare adapter: Workers Static Assets (Pages-compatible).",

package/src/worker-wrapper.mjs

@@ -48,8 +48,9 @@ export const WORKER_WRAPPER_SOURCE = `// AUTO-GENERATED by @takazudo/zfb-adapter
 //     \`pages/api/*.tsx\`) are served. EXCEPTION: when the asset 404
 //     carries a *styled* 404-page body (\`not_found_handling = "404-page"\`
 //     on Workers Static Assets, or the \`404.html\` convention on Pages —
-//     detected as an HTML document with a real Content-Length) AND the
-//     inner ALSO 404s with only the framework default body (Hono's
+//     detected as an HTML document by content-type; the assets binding
+//     streams every response and never sends a \`content-length\` header)
+//     AND the inner ALSO 404s with only the framework default body (Hono's
 //     default not-found, \`text/plain\` "404 Not Found", or a bare 404
 //     with no content-type), the earlier styled asset 404 is preferred
 //     over the inner's plain 404 — otherwise the styled \`404.html\` would
@@ -94,15 +95,17 @@ function assetHasStyled404Body(response) {
   // True iff an ASSETS 404 carries the site's *styled* 404 page.
   // Platform fact: \`not_found_handling = "404-page"\` (Workers Static
   // Assets) and the Pages \`404.html\` convention both serve that page as
-  // an HTML document — auto-detected \`content-type: text/html\` and a real
-  // \`Content-Length\` (it is a static file). \`not_found_handling = "none"\`
-  // and a bare Pages advanced-mode 404 send Cloudflare's default 404 with
-  // an empty / non-HTML body, so this returns false and the inner wins.
+  // an HTML document — auto-detected \`content-type: text/html\`. The
+  // Workers Static Assets binding streams every response (chunked
+  // locally, HTTP/2 framed in production) and never sends a
+  // \`content-length\` header, so content-type alone is the discriminator.
+  // \`not_found_handling = "none"\` sends Cloudflare's default 404 with
+  // NO headers at all (empty/non-HTML content-type), so this still
+  // returns false there and the inner wins.
   // Header-only (never reads the body) so it holds for HEAD too and leaves
   // the one-shot asset stream intact for a verbatim return.
   const contentType = (response.headers.get("content-type") || "").toLowerCase();
-  const contentLength = Number(response.headers.get("content-length") || "0");
-  return contentType.includes("text/html") && contentLength > 0;
+  return contentType.includes("text/html");
 }
 
 function innerIsFrameworkDefault404(response) {