react-starter-kit

React Starter Kit A full-stack monorepo template for building SaaS applications with React 19, tRPC, and Cloudflare Workers. Type-safe from database to UI, deployable to the edge in minutes. Highlights Type-safe full stack – TypeScript, tRPC, and Drizzle ORM create a single type contract from database to UI Edge-native – Three Cloudflare Workers (web, app, api) connected via service bindings Auth + billing included – Better Auth with email OTP, passkey, Google OAuth, organizations, and Stripe subscriptions Modern React – React 19, TanStack Router (file-based), TanStack Query, Jotai, Tailwind CSS v4, shadcn/ui Database ready – Drizzle ORM with Neon PostgreSQL, migrations, and seed data Fast DX – Bun toolchain, Vite, Vitest, Oxlint, Oxfmt, and pre-configured VS Code settings React Starter Kit is proudly supported by these amazing sponsors:      Technology Stack Layer Technologies Runtime Cloudflare Workers Frontend React 19, TanStack Router, Tailwind CSS v4, shadcn/ui, Jotai Marketing Astro Backend Hono, tRPC, Better Auth, Stripe Database Drizzle ORM, Neon PostgreSQL Toolchain Bun, TypeScript 7.0, Vite, Vitest, Oxlint, Oxfmt Monorepo Architecture ├── apps/ │ ├── web/ Astro marketing site (edge router, serves static + proxies to app/api) │ ├── app/ React 19 SPA (TanStack Router, Jotai, Tailwind CSS v4) │ ├── api/ Hono + tRPC API server (Better Auth, Cloudflare Workers) │ └── email/ React Email templates ├── packages/ │ ├── ui/ shadcn/ui components (new-york style) │ ├── core/ Shared types and utilities │ └── ws-protocol/ WebSocket protocol with type-safe messaging ├── db/ Drizzle ORM schemas, migrations, and seed data ├── infra/ Terraform (Hyperdrive connection pools, R2 storage) ├── docs/ VitePress documentation └── scripts/ Build automation and dev tools Each app deploys independently to Cloudflare Workers. The web worker routes /api/* to the API worker and app routes to the app worker via service bindings. Prerequisites Bun v1.4+ (replaces Node.js and npm) VS Code with our recommended extensions React Developer Tools browser extension (recommended) Cloudflare account for deployment Quick Start 1. Create Your Project Generate a new repository from this template, then clone it locally: git clone https://github.com/your-username/your-project-name.git cd your-project-name 2. Install Dependencies bun install 3. Configure Environment This project follows Vite env conventions: .env is committed and contains shared defaults/placeholders only (no real secrets) .env.local is git-ignored and should contain your real credentials .env.local values override .env cp .env .env.local # then replace placeholder values with real ones Also check wrangler.jsonc for Worker configuration and bindings. 4. Start Development # Launch all apps in development mode (web, api, and app) bun dev # Or, start specific apps individually bun web:dev # Marketing site bun app:dev # Main application bun api:dev # API server 5. Initialize Database Ensure DATABASE_URL is configured in your .env.local file, then set up the schema: bun db:push # Push schema directly (quick dev setup) bun db:seed # Seed with sample data (optional) bun db:studio # Open database GUI db:push is for local prototyping only. Staging and production apply migrations instead: bun db:migrate:staging, bun db:migrate:production. App URL React app http://localhost:5173 Marketing site http://localhost:4321 API server http://localhost:8787 Keep Your Project Updated When you want to bring in newer React Starter Kit changes, ask your coding agent to run the merge-seed skill (/merge-seed in Claude Code or $merge-seed in Codex). It merges upstream changes while preserving your project's identity and configuration. Start with a clean working tree; the Quick Start guide explains the workflow and its safety boundary. Production Deployment The short version. The deployment guide covers each step in full. 1. Provision Infrastructure Terraform creates the Hyperdrive configurations the API worker connects through: bun infra:production apply Paste the two IDs it prints into the hyperdrive block of apps/api/wrangler.jsonc. 2. Environment Setup Configure your production secrets in Cloudflare Workers: # Required – the API refuses to deploy without these bun wrangler secret put BETTER_AUTH_SECRET --config apps/api/wrangler.jsonc --env="" bun wrangler secret put RESEND_API_KEY --config apps/api/wrangler.jsonc --env="" # Google sign-in (optional – email OTP and passkeys work without it) bun wrangler secret put GOOGLE_CLIENT_ID --config apps/api/wrangler.jsonc --env="" bun wrangler secret put GOOGLE_CLIENT_SECRET --config apps/api/wrangler.jsonc --env="" # Stripe billing (optional – set all four to enable, or none; annual is extra) bun wrangler secret put STRIPE_SECRET_KEY --config apps/api/wrangler.jsonc --env="" bun wrangler secret put STRIPE_WEBHOOK_SECRET --config apps/api/wrangler.jsonc --env="" bun wrangler secret put STRIPE_STARTER_PRICE_ID --config apps/api/wrangler.jsonc --env="" bun wrangler secret put STRIPE_PRO_PRICE_ID --config apps/api/wrangler.jsonc --env="" bun wrangler secret put STRIPE_PRO_ANNUAL_PRICE_ID --config apps/api/wrangler.jsonc --env="" # optional All of these belong to the API worker, which is what --config selects – without it Wrangler has no worker to attach the secret to. Use --env staging for staging; production is the top-level config, selected explicitly with --env="". Non-sensitive vars like RESEND_EMAIL_FROM go in wrangler.jsonc directly. Set RESEND_EMAIL_FROM to an address on a domain you have verified with Resend. The default onboarding@resend.dev only delivers to your own inbox, and sign-in is email OTP – leave it and no one else can sign in. 3. Migrate the Production Database bun db:migrate:production # reads .env.production.local, and