// the find
clerk/t3-turbo-and-clerk
A t3 Turbo starter with Clerk as the auth provider.
A Turborepo monorepo starter combining Next.js 13, Expo (React Native), tRPC v10, Prisma, and Clerk for auth. Useful if you need a shared type-safe API between a web app and mobile app without setting up the plumbing yourself. It's a snapshot of a specific tech stack from mid-2023, not an actively maintained template.
End-to-end type safety across web and mobile through a shared tRPC router is the real value — changing an API procedure breaks both clients at compile time. The Turborepo setup with pnpm workspaces and a shared `packages/db` and `packages/api` is laid out cleanly with proper package boundaries. Clerk integration is minimal and correct: middleware protects routes, the publishable key is separated from the secret key, and the Expo OAuth redirect flow is documented. CI is set up with pnpm caching from the start, which is one less thing to figure out.
This repo hasn't been touched since June 2024 and was already aging at that point — it's on Next.js 13 pages router (not App Router), tRPC v10 (v11 is out), and React Native 0.70. Adopting it means immediately dealing with upgrade debt before writing any real code. The Expo publishable key is hardcoded in `app.config.ts` rather than sourced from environment variables, which is a footgun for anyone who doesn't read the README carefully. The database schema in `packages/db/prisma/schema.prisma` is a placeholder with no real models — you're getting project structure, not a working foundation. Also, the Discord OAuth requirement in the README is buried and easy to miss, causing a broken auth flow on first run.