SmashStack Field Manual
Production notes for adopting the TypeScript monorepo template without relearning the same deployment failures.
SmashStack is a production-ready TypeScript monorepo template for teams that would rather ship product than rebuild auth, deployment, database, job, admin, and docs plumbing from scratch.
What this manual is for
Use these docs to inspect the seams before adopting the template. The goal is not to hide complexity. The goal is to put the decisions, tradeoffs, and production fixes where senior developers can audit them fast.
Template reference
Understand the replaceable project values, package boundaries, and starting points.
Changelog
Track what changed in the template and why the defaults evolved.
Operating assumptions
| Area | Default |
|---|---|
| API | Hono on Cloudflare Workers with typed boundaries |
| App | TanStack Start with route-level data loading |
| Auth | Better Auth with split-domain deployment concerns documented |
| Data | D1 and Drizzle with edge constraints called out |
| Jobs | Trigger.dev packaged for background product flows |
First adoption pass
pnpm run init-project
pnpm install
pnpm devAfter the initializer runs, read the production fixes and package boundaries before adding product code. That is where the template saves the most senior engineering time.