@takazudo/zfb-adapter-cloudflare 0.1.0-next.52 → 0.1.0-next.54

package/dist/worker-wrapper.mjs

@@ -31,8 +31,7 @@ export const WORKER_WRAPPER_SOURCE = `// AUTO-GENERATED by @takazudo/zfb-adapter
 //     islands-…">). If we let the inner Hono router handle them first,
 //     it would dynamic-SSR the page WITHOUT the prod head injection
 //     (which is a build-time post-process, not a runtime concern), and
-//     islands would never hydrate. See zfb#XXX (filed by Wave 10 of
-//     the zudo-doc#1355 zfb-pipeline-gaps epic).
+//     islands would never hydrate.
 //   - On 404 from ASSETS, fall through to the inner zfb worker. This is
 //     where genuinely dynamic routes (\`prerender = false\`, e.g.
 //     \`pages/api/*.tsx\`) are served.
@@ -68,6 +67,16 @@ function isAssetProbeMethod(method) {
 export default {
   async fetch(request, env, ctx) {
     if (isAssetProbeMethod(request.method) && canDelegateToAssets(env)) {
+      // Trade-off: every GET/HEAD request that matches a prerendered route pays
+      // the cost of one env.ASSETS.fetch() round-trip before the inner worker
+      // sees it.  The upside is that CF Pages' asset server handles trailing-
+      // slash canonicalisation (e.g. /docs/foo → 308 → /docs/foo/) and serves
+      // the build-time head-injected HTML with the hashed <link>/<script> tags.
+      // If we skipped this probe, prerendered routes would be dynamic-SSR'd by
+      // the inner Hono router without the prod head injection, and islands would
+      // never hydrate.  For purely dynamic apps (prerender=false everywhere) the
+      // extra round-trip is pure overhead; splitting the wrapper into two
+      // variants is the accepted future escape hatch for that case.
       const assetResponse = await env.ASSETS.fetch(request);
       if (assetResponse.status !== 404) {
         return assetResponse;

package/package.json

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

package/src/worker-wrapper.mjs

@@ -31,8 +31,7 @@ export const WORKER_WRAPPER_SOURCE = `// AUTO-GENERATED by @takazudo/zfb-adapter
 //     islands-…">). If we let the inner Hono router handle them first,
 //     it would dynamic-SSR the page WITHOUT the prod head injection
 //     (which is a build-time post-process, not a runtime concern), and
-//     islands would never hydrate. See zfb#XXX (filed by Wave 10 of
-//     the zudo-doc#1355 zfb-pipeline-gaps epic).
+//     islands would never hydrate.
 //   - On 404 from ASSETS, fall through to the inner zfb worker. This is
 //     where genuinely dynamic routes (\`prerender = false\`, e.g.
 //     \`pages/api/*.tsx\`) are served.
@@ -68,6 +67,16 @@ function isAssetProbeMethod(method) {
 export default {
   async fetch(request, env, ctx) {
     if (isAssetProbeMethod(request.method) && canDelegateToAssets(env)) {
+      // Trade-off: every GET/HEAD request that matches a prerendered route pays
+      // the cost of one env.ASSETS.fetch() round-trip before the inner worker
+      // sees it.  The upside is that CF Pages' asset server handles trailing-
+      // slash canonicalisation (e.g. /docs/foo → 308 → /docs/foo/) and serves
+      // the build-time head-injected HTML with the hashed <link>/<script> tags.
+      // If we skipped this probe, prerendered routes would be dynamic-SSR'd by
+      // the inner Hono router without the prod head injection, and islands would
+      // never hydrate.  For purely dynamic apps (prerender=false everywhere) the
+      // extra round-trip is pure overhead; splitting the wrapper into two
+      // variants is the accepted future escape hatch for that case.
       const assetResponse = await env.ASSETS.fetch(request);
       if (assetResponse.status !== 404) {
         return assetResponse;