fix(docs): get docs.stackpanel.com/docs/* working again

[cooper (czxtm)]

Summary

Fixes docs.stackpanel.com/docs/* (and every other dynamic Next route on the docs Worker) returning 500 Internal Server Error while / and /api/search work.

This turned out to be three separate bugs stacked on top of each other, where each one masked the next. Each commit peels off one layer.

1. Deploy-time: alchemy re-bundles the OpenNext entrypoint

alchemy@2.0.0-beta.20's Cloudflare.Worker.prepareBundle runs .open-next/worker.js through cloudflareRolldown even when isExternal: true. The re-bundle rewrites OpenNext's runtime import("./server-functions/default/handler.mjs") so its wrapper resolver returns undefined and the deployed Worker dies on first request with

TypeError: Cannot destructure property 'name' of '(intermediate value)'
    at worker.js:1:23445 in createGenericHandler

This is what was failing every Deploy Docs CI job since the alchemy@2 migration — the user-facing 500s were the previous still-running deploy.

Fix: patch alchemy (via bun's patchedDependencies) to add WorkerProps.bundle?: boolean (default true). When false, prepareBundle reads props.main and uploads it byte-for-byte (hash = sha256(content)) — no rolldown step. Same patch is up on my fork as the proposed upstream PR: czxtm/alchemy-effect@df6ed57 / standalone repro at https://github.com/czxtm/repro-alchemy-bundle-false.

2. Build-time: OpenNext's worker.js isn't self-contained

OpenNext's .open-next/worker.js is a ~2KB entrypoint with explicitly comments saying the static ./cloudflare/*.js imports "Will be resolved by wrangler build". Uploading byte-for-byte gives Uncaught Error: No such module "cloudflare/images.js".

Fix: run wrangler deploy --dry-run --outdir=.open-next/dist --minify after opennextjs-cloudflare build. Wrangler bundles the static imports while preserving the dynamic import() paths the way OpenNext expects. Point main: at the wrangler output and keep bundle: false so alchemy uploads the wrangler artifact byte-for-byte. (Without --minify, the bundle is 70 MiB uncompressed — over CF's 64 MiB Workers script limit. With --minify, 32 MiB uncompressed / 4 MiB gzipped after fix #3.)

3. Runtime: fumadocs-typescript calls fs.mkdir on every dynamic page render

Once the Worker actually deployed, runtime traffic surfaced the bug the user was hitting all along. wrangler tail on docs.pr-20.stackpanel.com:

GET /docs - Ok @ 12:55:10
  (error) Error: [unenv] fs.mkdir is not implemented yet!
      at l6 (worker.js:112349:269)
      at worker.js:112349:8151

That stack lands inside ts-morph's FileSystemDocumentCache.mkdir, pulled in transitively from apps/docs/src/mdx-components.tsx:

mdx-components.tsx
  → fumadocs-typescript            (createGenerator + AutoTypeTable UI)
  → fumadocs-typescript/ui         (AutoTypeTable React component)
  → @ts-morph/common + ts-morph    (TS compiler API + virtual FS)

createFileSystemGeneratorCache(".next/fumadocs-typescript") calls fs.mkdir on first render, which the Workers nodejs_compat polyfill (unenv) doesn't implement.

The runtime registration was dead code: <AutoTypeTable /> in MDX is expanded at build time by remarkAutoTypeTable in source.config.ts, so the rendered output never contains a live <AutoTypeTable> element — verified rg AutoTypeTable apps/docs/content returns no matches.

Fix: drop AutoTypeTable and the runtime createGenerator from mdx-components.tsx. Drops ts-morph entirely from the runtime worker bundle (~25 MiB).

Verification

PR preview at docs.pr-20.stackpanel.com:

Route	Before	After
/	200	200
/docs	500	200 (<title>Stackpanel</title>)
/docs/agent	500	200 (<title>CLI / Agent</title>)
/docs/cli	500	200
/docs/reference	500	200
/api/search	200	200

Bundle size: 70 MiB → 32 MiB uncompressed, ~10 MiB → 4 MiB gzipped.

Cleanup followups

Filed as separate issues for after merge:

• stackpanel-49t: closeable — alchemy bundle: false patch + the docs fixes are this PR. Drop the patch + the bundle: false prop once cloudflareRolldown's dynamic-import handling is fixed upstream (PR proposed at https://github.com/czxtm/alchemy-effect ready to be opened against alchemy-run/alchemy-effect).
• New: revisit re-enabling <AutoTypeTable /> MDX with a non-FS cache implementation (or omitting the runtime cache entirely) if we ever want to use it in MDX content.

[cursor]

PR Summary

Medium Risk
Touches deployment-critical behavior by patching a third-party infra tool (alchemy) and changing how the docs Worker bundle is uploaded, though the new behavior is opt-in (bundle: false) with a default preserving existing behavior elsewhere.

Overview
Fixes Docs Cloudflare Worker deploy/runtime failures by opting out of alchemy’s rolldown re-bundling for the prebuilt OpenNext .open-next/worker.js.

This introduces a Bun patchedDependencies patch to alchemy@2.0.0-beta.20 adding Cloudflare.Worker bundle?: boolean (default true); when set to false, prepareBundle uploads main byte-for-byte and hashes it via sha256 instead of running rolldown. The docs deploy (apps/docs/alchemy.run.ts) now sets bundle: false alongside isExternal: true to keep OpenNext’s dynamic imports intact.

Lockfile/package metadata is updated to apply the patch (and cleans up stale bun2nix entries), and issues.jsonl is updated with new/expanded tracking items around the deploy regressions and state-store bootstrap.

^{Reviewed by Cursor Bugbot for commit 1d47562. Configure here.}

[github-actions]

Preview pr-20 has been destroyed.

[github-actions]

Docs preview pr-20 has been destroyed.