cloudflare

Run vite build, then deploy with wrangler deploy -c dist/rsc/wrangler.json. The build emits a deployable Worker configuration under the RSC environment output; never deploy the source main from the root config because Wrangler cannot reconstruct Rango's Vite virtual modules.

Create resources with wrangler d1 create and wrangler kv namespace create, then copy the returned IDs into wrangler.json under d1_databases and kv_namespaces. Keep binding names identical in wrangler.json and your AppBindings TypeScript interface so ctx.env.DB resolves correctly.

Calling response.text() or response.arrayBuffer() on the Rango response drains the RSC/SSR stream. Rewrap with new Response(response.body, response) when only headers must change, and avoid diagnosing streaming with wrangler dev since local gzip compression can buffer responses.

The Cloudflare Vite plugin runs the Worker in workerd during vite dev and vite preview with the same binding shape as deployment. However, preview loads .dev.vars copied during the last build, so rebuild after changing secrets, and run your behavior suite against both dev and preview.

Use Stripe 22, which publishes a workerd export using fetch and SubtleCrypto, and call the asynchronous Stripe.webhooks.constructEventAsync with the raw request body. Read the exact bytes via ctx.request.text() since signature verification requires the original payload.

Vite's CORS middleware answers preflight OPTIONS before the Worker in both dev and preview, so a passing preview preflight does not prove your route's own OPTIONS branch works. Set server.cors and preview.cors to false and assert the full CORS headers on real responses.