You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(web): migrate web frontend to Vercel + switch CI web deploy to Vercel
The Next.js web bundle exceeds Cloudflare's free Worker size limit, so the
frontend moves to Vercel (free Hobby for a non-commercial OSS demo) while the
all-Cloudflare backend (DOs/Workflows/agent loop) stays on the worker chain.
The app has zero CF runtime coupling (HTTP-only backend access), so it builds
as a standard Next.js app.
- next.config: Vercel-safe — omit output:standalone on Vercel (VERCEL env),
dev-guarded dynamic import of the OpenNext shim (bracket-notation env access
for noPropertyAccessFromIndexSignature).
- apps/web/package.json: packageManager pnpm@10.33.2 so Vercel uses pnpm
(npm can't parse the workspace catalog: protocol).
- .vercelignore: exclude the legacy /cheatcode tree (special files break the CLI)
+ non-code dirs, ANCHORED to root so nested source dirs (apps/web/.../docs)
aren't excluded. Vercel rootDirectory=apps/web; deploy from repo root so the
whole pnpm workspace uploads.
- CI: replace the dead Cloudflare deploy-web job with deploy-web-vercel
(vercel deploy --prod; build env lives in the Vercel project). gitignore .vercel.
0 commit comments