clerk/t3-turbo-and-clerk

A t3 Turbo starter with Clerk as the auth provider.

Summary

clerk/t3-turbo-and-clerk is a monorepo starter that combines the T3 stack (Next.js, tRPC, Prisma, TypeScript) with Turborepo and Clerk for authentication. It ships two runnable apps—a Next.js 13 web client and an Expo mobile client—that share a typed API and database layer. The repository is marked as archived, so it is best treated as a reference template rather than an actively maintained project.

What it is useful for

This template is useful when you need a head start on a full-stack TypeScript project where the same backend powers both a web app and a mobile app. The shared packages/api package defines a tRPC v10 router that both the Next.js and Expo apps consume, giving you end-to-end type safety from the database call to the UI. Clerk handles sign-in across both platforms, and the README notes that you must enable Discord as an OAuth provider in the Clerk dashboard before sign-in will work end-to-end. The packages/db package wraps Prisma for typesafe queries, which the README connects to a database via pnpm db-push. Because the project ships both Next.js and Expo in one Turborepo, it is a reasonable reference for monorepo layouts, shared environment configuration, and CI workflows (the repo includes a GitHub Actions CI workflow with pnpm caching).

How engineers can use it

The README's documented quick start is: pnpm i to install, cp .env.example .env to seed environment variables, then pnpm db-push to apply the schema. For the Expo app you also have to paste your Clerk publishable key into apps/expo/app.config.ts (the README is explicit that Expo does not read from .env). The README recommends changing the dev script in apps/expo/package.json to expo start --ios or expo start --android if you want to launch a simulator instead of scanning a QR code with Expo Go. For deployment, the README walks through Vercel for the Next.js app, with notes warning against SQLite on serverless and suggesting a Postgres provider like Railway, and EAS Build plus EAS Submit for the Expo app. Because the repository is archived, engineers adopting it should verify the upstream create-t3-turbo project and current Clerk Expo guidance before basing new work on it.