Deploying an Astro v6 site to Cloudflare Workers

This post corresponds to PR 2 in the build series.

What shipped

Cloudflare Workers as the deployment target via @astrojs/cloudflare
- Upgraded to the Astro 6-era adapter (@astrojs/cloudflare@13.x) to match Astro v6
output: "server" (while still prerendering content-driven routes)
Wrangler config aligned with Astro 6
- main: @astrojs/cloudflare/entrypoints/server
- assets binding: serve ./dist static assets alongside the Worker
A working local lifecycle that matches production closely
- astro dev + astro preview running on Cloudflare’s workerd runtime
A “boring” manual deploy path (wrangler deploy)

Cloudflare is already the platform constraint for this series.
Astro v6’s direction is explicitly “Workers-friendly”; I want to follow defaults.
I want local development and preview to be as close to production as possible.

astro preview runs using Cloudflare’s workerd runtime, which is the point: it’s close to production.
Static routes can still be prerendered even in server mode (export const prerender = true).
- Reference: Astro “Rendering modes” docs: https://docs.astro.build/en/basics/rendering-modes/
- Error reference (why the export must be a simple static boolean): https://docs.astro.build/en/reference/errors/invalid-prerender-export
If you remove prerender from a content-driven dynamic route, getStaticPaths() can be ignored in server mode and you’ll hit runtime errors (we saw this happen and fixed it by re-enabling prerendering on /posts/[...id]).

Later: auto-deploy to production from main, and generate preview deploys for PRs/branches.