Saraan Asim
NexNest is a monorepo template I wrote in August 2025. It became the standard starting point for new projects that pair a Next.js frontend with a NestJS backend. It is public on my GitHub.
What is in it
- Two apps and one shared package.
apps/frontendis Next.js 15 with the App Router and Tailwind CSS v4.apps/backendis NestJS 11.packages/sharedholds the config, constants, types and utilities both apps import. - Turborepo and pnpm workspaces. Turborepo runs build, lint, test and type-check across the workspace, and builds a package’s dependencies before the package itself.
- CI on every push and pull request. GitHub Actions installs with a frozen lockfile, then runs type-check, lint, tests, the build, and a dependency audit that fails the run on moderate or worse findings.
- Commit rules. Husky hooks and commitlint enforce conventional commit messages.
- Docker for three environments. Separate Compose files for development, staging and production.
- A setup script. One command renames the project and the package scope, so a new project starts with its own name everywhere.
Why I built it
Consistency across teams. When every team starts a project its own way, moving between projects means relearning the layout, the scripts and the CI each time. With one template, every new project has the same folders, the same commands and the same checks, so anyone on another team already knows where things are.
One workspace also means the frontend and the backend share types from packages/shared. A breaking change to a request or response type fails the type-check in CI before it reaches a pull request review.
Why a template
Every new project used to start with the same day or two of setup: lint rules, CI, Docker, environment files, folder layout. A template makes those decisions once.
The same layout shows up in the products I have built since. SiftSight runs its candidate, recruiter and admin apps from one Next.js and NestJS monorepo, and Terravive is a monorepo too.