New Example Proposal: Full-stack monorepo template with Vite, Expo, Express, Prisma, and shared compiled packages

[IamAyaanSk]

Hey everyone 👋

I've been building a monorepo-based product and found myself repeatedly setting up the same patterns, compiled internal packages, shared API contracts, database layer, env validation, etc. So I extracted it into a reusable template called Turbo Stack.

---

What it is

A batteries included Turborepo template with 3 apps and 7 shared packages, all wired together with ESM, TypeScript, and pnpm catalogs.

Apps

• Web — Vite 8 + React 19 + TanStack Router (file-based, auto code-split) + TanStack Query
• Server — Express 5 with versioned API routes, helmet, cors, morgan
• Mobile — Expo 57 with Expo Router

Shared Packages

• @repo/ui-web — shadcn/ui components + Tailwind CSS 4 (shared component library)
• @repo/api-contract — Zod schemas defining API request/response types (shared between client and server)
• @repo/api-client — Axios-based HTTP client with TanStack Query hooks (used by web and mobile)
• @repo/db — Prisma 7 + PostgreSQL with driver adapter
• @repo/env — Zod-based environment variable validation
• @repo/shared-validations — Reusable Zod schemas shared across the entire repo
• @repo/typescript-config — Shared base tsconfig

Technologies used

Layer	Technology
Monorepo	Turborepo, pnpm Workspaces
Web	Vite 8, React 19, Tailwind CSS 4, shadcn/ui
Routing	TanStack Router (File-based, Code Splitting)
Data Fetching	TanStack Query
Mobile	Expo 57, React Native, Expo Router
API	Express 5
Database	Prisma 7, PostgreSQL
Validation	Zod 4
Language	TypeScript 6 (ESM, NodeNext)
Linting & Formatting	oxlint, oxfmt
Package Manager	pnpm 11

Repo

🔗 GitHub — turbo-stack

Would love to hear feedback, suggestions, or if anyone finds this useful for their own projects. Happy to answer questions about any of the patterns! Also wondering whether this would be a good fit for the community-maintained examples.

[farfromexact]

This looks like a useful community example, but I would validate it as a clean Turborepo template before asking for inclusion. The important test is that a new user can clone it, install the documented versions, run the web, API, and mobile apps, and understand the task graph without reverse-engineering the stack.

I would make the example boundaries explicit:

• apps/web, apps/mobile, and apps/api should have independent dev and build commands
• packages should expose the shared API contract and generated Prisma client through normal workspace dependencies
• turbo.json should document the build dependency chain and outputs, including any generated client or Expo artifacts
• strict environment handling should list the variables needed by each task, instead of relying on an untracked root .env
• CI should run the same filtered build and typecheck commands as the README

The current stack is broad enough that version drift will be the main maintenance cost. A small compatibility table for Node, pnpm, Expo, Prisma, and TypeScript, plus a CI smoke test and a turbo prune or deployment example, would make this much more convincing as a community-maintained example than a large feature list alone.

[IamAyaanSk]

Hey @farfromexact, thanks for checking out!

I agree with your takes as this example implements a broad tech stack and it can feel opinionated specifically on the api contract and env packages which would not fit for some teams.
It is quite logical to not include this as an example and rather just keep it as a template that is publicly available in my repository 😉

This template can be useful for developers and teams who want a quick complete setup and are happy to understand or change some of the conventions. Additionally all the mentioned boundaries were kept in mind when I was setting this up!!

Thanks!!