A starter template for building full-stack Next.js applications with end-to-end type safety using tRPC and Prisma.
tRPC Next Prisma Starter is a starter template for building full-stack TypeScript applications with Next.js, tRPC, and Prisma. It provides a pre-configured setup that ensures end-to-end type safety from the database to the frontend, streamlining development and reducing runtime errors. The template includes testing, CI/CD, and deployment configurations to help developers quickly launch production-ready applications.
Full-stack TypeScript developers building Next.js applications who want a type-safe, opinionated starter with integrated database access and testing.
Developers choose this template for its seamless integration of tRPC and Prisma, which eliminates manual API type definitions and ensures type safety across the entire stack. It offers a production-ready foundation with built-in testing, linting, and deployment setups, saving significant initial configuration time.
🚀 tRPC starter repo with E2E-testing
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses tRPC to automatically infer types between frontend and backend, eliminating manual API definitions and catching errors early, as highlighted in the README's emphasis on E2E typesafety.
Includes pre-configured E2E testing with Playwright, unit testing with Vitest, and CI via GitHub Actions, ensuring robust quality assurance from the start, as noted in the features list.
Comes with ESLint, Prettier, and recommended VSCode extensions out of the box, streamlining the development workflow and reducing setup time, as mentioned in the tooling section.
Integrates Prisma for type-safe database queries and migrations, ensuring data consistency from schema to application logic, with examples in the Prisma schema file.
Heavily couples the project to tRPC, Prisma, and Postgres, making it difficult to switch to alternatives like GraphQL or other ORMs without significant refactoring.
Requires running a local Postgres instance and uses pnpm, adding complexity compared to simpler starters that might use SQLite or npm/yarn, as indicated in the setup requirements.
Enforces specific patterns like tRPC routers and file structures, limiting customization for teams with different architectural preferences or legacy codebases.