A full-stack monorepo template for NestJS and Prisma with Yarn Workspaces, featuring GraphQL, REST, and JWT.
Nest Prisma Monorepo is a starter template for building full-stack applications using NestJS and Prisma in a monorepo structure. It provides a pre-configured setup with shared libraries, authentication, API layers, and development tools to accelerate project initialization. The template solves the complexity of setting up a scalable monorepo with integrated database access and code sharing.
Full-stack or backend developers starting new projects with NestJS and Prisma who want a structured, reusable monorepo foundation. It's also suitable for teams needing consistent tooling and shared modules across multiple apps.
Developers choose this template for its opinionated yet flexible structure, which reduces boilerplate and enforces best practices for monorepo management. It uniquely combines NestJS conventions with Prisma utilities and ready-to-use CI/CD workflows.
🐈 NestJS + Prisma + Yarn Workspaces (Monorepo) full-stack project template
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Follows NestJS conventions with clear separation of apps and libraries, enabling scalable development and code sharing, as outlined in the structure section.
Includes ESLint, Prettier, and GitHub Actions CI ready to use, reducing setup time and enforcing code quality from the start.
Offers both GraphQL (code-first) and REST APIs with Swagger documentation, cloned from an established starter template for reliability.
Prisma schema and client are shared via a library, allowing consistent database access across apps, as explained in the note about Prisma.
The web app is just a static HTML file, requiring significant additional work to integrate frameworks like Next.js or Angular, which the README admits is intentional but adds initial overhead.
Uses Yarn berry with Plug'n'Play disabled due to lack of support from NestJS and Prisma, limiting package management optimizations and potential performance benefits.
Requires creating .env files in multiple locations and replacing all 'acme' references with organization names, adding setup complexity and room for error.