Skip to content

CA1: the storefront on Workers - #2

Merged
pullely merged 1 commit into
mainfrom
orun/CA-2-the-storefront-on-workers
Oct 28, 2026
Merged

pullely merged 1 commit into
mainfrom
orun/CA-2-the-storefront-on-workers

Conversation

@pullely

@pullely pullely commented Oct 28, 2026

Copy link
Copy Markdown
Contributor

bigcommerce/catalyst (6faa4b5, @bigcommerce/catalyst-core 1.13.1, MIT): core/ in apps/web and its client and eslint-config-catalyst packages in packages/, built by @opennextjs/cloudflare 1.20.11 into one Worker with Static Assets — Next 16.3.8 (inside upstream's ~16.3.4), next build --webpack (Turbopack's middleware bundle cannot resolve @opentelemetry/api). The R2 incremental cache (infra/terraform/cloudflare-r2), the sharded Durable Object tag cache and the Durable Object revalidation queue, as the commerce baseline has them, and Catalyst's own Cloudflare KV adapter for its route lookups (CATALYST_ROUTES_KV, infra/terraform/cloudflare-kv — kv-redis-starter's root). Catalyst caches through Next's fetch cache, not Cache Components, so nothing upstream is turned off. The GraphQL types come from BigCommerce's published Storefront schema (apps/web/bigcommerce.graphql, from bigcommerce/checkout-sdk-js), so nothing needs a store. With no store hash and token (lib/bigcommerce-connection.ts) the build reads no settings, the proxy and the storefront layout send every page to / and / says "Connect your BigCommerce store"; the store's hash, token and channel are optional secrets the build reads and the deploy sets as Worker secrets (tooling/wire/worker-secrets.mjs). worker.ts hands Auth.js its key: AUTH_SECRET, else one the Worker generates and keeps in KV. @vercel/otel loads only with an OTLP endpoint; SITE_NAME (lib/site.ts) is the fallback store name; /api/health. The lockfile is seeded from upstream's, typescript-eslint held at its 8.28. typecheck, lint, test (upstream's 286 and tests/web's 24) and build are green; the Worker is 3.36 MiB gzipped (Workers Paid).

🤖 Generated with Claude Code

bigcommerce/catalyst (6faa4b5, @bigcommerce/catalyst-core 1.13.1, MIT): core/ in apps/web and its client and eslint-config-catalyst packages in packages/, built by @opennextjs/cloudflare 1.20.11 into one Worker with Static Assets — Next 16.3.8 (inside upstream's ~16.3.4), next build --webpack (Turbopack's middleware bundle cannot resolve @opentelemetry/api). The R2 incremental cache (infra/terraform/cloudflare-r2), the sharded Durable Object tag cache and the Durable Object revalidation queue, as the commerce baseline has them, and Catalyst's own Cloudflare KV adapter for its route lookups (CATALYST_ROUTES_KV, infra/terraform/cloudflare-kv — kv-redis-starter's root). Catalyst caches through Next's fetch cache, not Cache Components, so nothing upstream is turned off. The GraphQL types come from BigCommerce's published Storefront schema (apps/web/bigcommerce.graphql, from bigcommerce/checkout-sdk-js), so nothing needs a store. With no store hash and token (lib/bigcommerce-connection.ts) the build reads no settings, the proxy and the storefront layout send every page to / and / says "Connect your BigCommerce store"; the store's hash, token and channel are optional secrets the build reads and the deploy sets as Worker secrets (tooling/wire/worker-secrets.mjs). worker.ts hands Auth.js its key: AUTH_SECRET, else one the Worker generates and keeps in KV. @vercel/otel loads only with an OTLP endpoint; SITE_NAME (lib/site.ts) is the fallback store name; /api/health. The lockfile is seeded from upstream's, typescript-eslint held at its 8.28. typecheck, lint, test (upstream's 286 and tests/web's 24) and build are green; the Worker is 3.36 MiB gzipped (Workers Paid).

Co-Authored-By: Claude <noreply@anthropic.com>
Orun-Task: CA-2
@pullely
pullely merged commit 64ba8b2 into main Oct 28, 2026
2 checks passed
@pullely
pullely deleted the orun/CA-2-the-storefront-on-workers branch October 28, 2026 12:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants