A monorepo boilerplate built with Turborepo and NestJS.
# Clone the repository
git clone https://github.com/vndevteam/nestjs-turbo.git
# Create environment variables file.
cp apps/admin-api/.env.example apps/admin-api/.env
cp apps/user-api/.env.example apps/user-api/.env
# Install dependences.
pnpm install
When you use this template, try follow the checklist to update your info properly
- Change the author name in
LICENSE
- Change configurations in
.env
- Remove the
.github
folder which contains the funding info - Clean up the README.md file
This project includes the following packages/apps:
docs
: a Next.js appweb
: another Next.js app@repo/ui
: a stub React component library shared by bothweb
anddocs
applications@repo/eslint-config
:eslint
configurations (includeseslint-config-next
andeslint-config-prettier
)@repo/typescript-config
:tsconfig.json
s used throughout the monorepo
Each package/app is 100% TypeScript.
This project has some additional tools already setup for you:
- TypeScript for static type checking
- ESLint for code linting
- Prettier for code formatting
To build all apps and packages, run the following command:
cd my-turborepo
pnpm build
To develop all apps and packages, run the following command:
cd my-turborepo
pnpm dev
Turborepo can use a technique known as Remote Caching to share cache artifacts across machines, enabling you to share build caches with your team and CI/CD pipelines.
By default, Turborepo will cache locally. To enable Remote Caching you will need an account with Vercel. If you don't have an account you can create one, then enter the following commands:
cd my-turborepo
npx turbo login
This will authenticate the Turborepo CLI with your Vercel account.
Next, you can link your Turborepo to your Remote Cache by running the following command from the root of your Turborepo:
npx turbo link
Learn more about the power of Turborepo: