kriasoft/react-starter-kit — 23.7k★ trên GitHub (TypeScript). Modern React starter kit with Bun, TypeScript, Tailwind CSS, tRPC, Stripe, and Cloudflare Workers. Production-ready monorepo for building fast web apps.
Tóm tắt dựng từ metadata GitHub của chính dự án — chưa có bài review TopGit. Trang sẽ tự động cập nhật khi bài review đầy đủ được xuất bản.
VÌ SAO CHƯA CÓ REVIEW
TopGit viết bài đầy đủ cho repo có nhiều sao nhất và được yêu cầu nhiều nhất. Trang này là snapshot trong thời gian chờ — xem README gốc ở tab READ ME.
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
├── 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.
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 [email protected] 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 only that file
4. Build and Deploy
# Builds, then deploys api -> app -> web (service-binding targets first)
bun deploy:staging
bun deploy:production
CI runs the same script, so a release from your machine and one from GitHub Actions cannot drift.
Backers
Contributors
Need Help?
Documentation covers auth, database, billing, deployment, and more.
Our AI assistant is trained on this codebase – ask it anything on ChatGPT or Gemini. Try these questions:
How do I add a new tRPC endpoint?
Help me create a database table
How does authentication work?
Explain the project structure
How do I deploy to Cloudflare?
Add a new page with routing
How do I send emails?
Contributing
See the Contributing Guide to get started. Check good first issues or join Discord for discussion.
kriasoft/react-starter-kit thuộc nhóm Frontend trên TopGit, cùng 20 topic GitHub. Trang Trending và Topics liệt kê các repo cùng số sao và cùng ngôn ngữ để so sánh.
Đọc thêm về kriasoft/react-starter-kit ở đâu?
Trang TopGit này là một snapshot — tab "Readme" hiển thị nguyên văn README của repo (đã bỏ link, giữ ảnh). Repo GitHub ở github.com/kriasoft/react-starter-kit là nguồn chính thức.
kriasoft/react-starter-kit có phải mã nguồn mở không?
Có — kriasoft/react-starter-kit phát hành theo license MIT, nghĩa là mã nguồn mở để đọc, fork và (tùy license) tái sử dụng. Mã: github.com/kriasoft/react-starter-kit.
kriasoft/react-starter-kit có trang demo không?
Dự án có trang chủ ở https://reactstarter.com. Tab "Readme" ở trang này thường có ảnh chụp và hướng dẫn bắt đầu nhanh.
kriasoft/react-starter-kit dùng license gì?
kriasoft/react-starter-kit phát hành theo license MIT. Nên mở file LICENSE trên GitHub để xác nhận — license metadata đôi khi lệch với thực tế dự án.
kriasoft/react-starter-kit là gì?
kriasoft/react-starter-kit (kriasoft/react-starter-kit) là dự án TypeScript trên GitHub. Theo mô tả gốc: Modern React starter kit with Bun, TypeScript, Tailwind CSS, tRPC, Stripe, and Cloudflare Workers. Production-ready monorepo for building fast web apps.
Vì sao kriasoft/react-starter-kit được xếp vào nhóm Frontend?
TopGit xếp kriasoft/react-starter-kit vào nhóm Frontend dựa trên GitHub topics và mô tả của repo (gắn thẻ: "better-auth", "boilerplate", "bun"). Việc phân loại dựa trên metadata thật của repo, không phải đoán theo cảm tính biên tập.
Đọc đầy đủ README ở tab phía trên.
react-starter-kit có đáng để bạn bỏ thời gian?
ChatGPT, Claude và Perplexity đều đọc được trang này. Hỏi thử xem họ nghĩ gì về react-starter-kit.