The Cloudflare Stack

Build one coherent Cloudflare-native application. Keep server-only code inside the Worker runtime, access Cloudflare resources through typed bindings, and prove the real authentication, database, and storage flows before calling the work complete.

Stack contract

• Application: TanStack Start with React, deployed to Cloudflare Workers through the official @cloudflare/vite-plugin integration.
• Build: Vite 8. Check plugin compatibility with Vite 8's Rolldown/Oxc toolchain; do not silently downgrade to Vite 7.
• Authentication: Better Auth using its official Drizzle adapter.
• Database: Drizzle ORM with either Cloudflare D1 or an external PostgreSQL/MySQL database reached through Hyperdrive.
• UI: Tailwind CSS v4, shadcn/ui, and coss ui.
• Object storage: Cloudflare R2. R2 is the Cloudflare product; “Cloudflare S3” means its S3-compatible API, not AWS S3.
• Language: TypeScript with generated Cloudflare binding types.

Preserve the package manager, lockfile, and repository structure in an existing project. For a new project, check whether Bun is available with bun --version. If it succeeds, use Bun consistently for package installation, scripts, tests, and one-off package executables. Otherwise use pnpm unless the user requests another package manager.

Package manager policy

When Bun is selected: