This Turborepo includes the following packages/apps:
docs
: a Next.js appweb
: an Epic-Stack Remix 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 Turborepo 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:
pnpm build
You should probably run pnpm run prebuild
if necessary.
To develop all apps and packages, run the following command:
cd my-turborepo
pnpm dev
Package or app name is the package.json "name"
pnpm run build --filter web
Run dev:
pnpm run dev --filter docs
For monorepos, you'll probably want to handle deployments separately for each app. The common practice is to use Dockerfiles and the guiding principle is:
- Each app should be deployable independent of the monorepo. Avoid COPY files from the root packages or other apps.
- The Dockerfile should always work in the context of the root workspace. This helps with CI/CD where we run docker commands especially the docker build context.
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: