npx skills add ...
npx skills add openai/plugins --skill turborepo
npx skills add openai/plugins --skill turborepo
Turborepo expert guidance. Use when setting up or optimizing monorepo builds, configuring task caching, remote caching, parallel execution, or the --affected flag for incremental CI.
You are an expert in Turborepo v2.8 — "the build system for agentic coding" — a high-performance build system for JavaScript/TypeScript monorepos, built by Vercel with a Rust-powered core.
--affected flag runs only changed packages + dependentsturbo devtools (2.8+)turbo.json from any package, not just root (2.7+)turbo docs returns markdown responses optimized for AI agents (2.8+)The turbo.json file defines your task dependency graph. Here are comprehensive examples:
dependsOn: ["^build"] — Run build in dependencies first (^ = topological)dependsOn: ["build"] — Run build in the same package first (no ^)outputs — Files to cache (build artifacts)inputs — Files that affect the task hash (default: all non-gitignored files)env — Environment variables that affect the task hashcache: false — Skip caching (for dev servers, codegen)persistent: true — Long-running tasks (dev servers)globalDependencies — Files that invalidate all task caches when changedglobalEnv — Env vars that invalidate all task caches when changedRun tasks in specific packages or subsets of your monorepo:
| Pattern | Meaning |
|---|---|
web | Only the web package |
web... | web and all its dependencies |
...web | web and all its dependents |
...web... | web, its dependencies, and its dependents |
./apps/* | All packages in the apps/ directory |
[main] | Packages changed since main branch |
{./apps/web}[main] | web only if it changed since main |
!docs | Exclude the docs package |
Run tasks in watch mode for development — re-executes when source files change:
Watch mode respects the task graph — if test depends on build, changing a source file re-runs build first, then test.
persistent: true in turbo.json: The task itself is long-running (e.g., next dev). Turbo starts it and keeps it alive.turbo watch: Turbo re-invokes the task on file changes. Use for tasks that run and exit (e.g., vitest run, tsc --noEmit).Enforce architectural constraints across your monorepo with boundaries in turbo.json:
This enforces:
turbo boundariesInspect your task dependency graph:
The dry run output shows:
Note:
turbo docsoutput is optimized for AI coding agents — markdown format preserves context windows. The docs site also includes sample prompts for common tasks you can copy directly into your agent.
Package configs can now extend from any workspace package, not just the root:
The most important optimization for CI pipelines:
This performs intelligent graph traversal:
Turborepo is the recommended orchestration layer for Vercel's Microfrontends architecture — composing multiple independently-deployed apps behind a single URL.
Each micro-app is a separate Vercel project with its own build and deploy lifecycle:
Use Turborepo's dependency graph to share code without coupling deploys:
Shared packages (ui, auth, config) are built first via ^build, then each micro-app builds against the latest shared code. Remote caching ensures shared package builds are never repeated across micro-app deploys.
Next.js multi-zones let each micro-app own a URL path prefix while sharing a single domain:
Combine with Turborepo boundary rules to enforce architectural isolation:
| Scenario | Recommended? |
|---|---|
| Multiple teams owning independent features | Yes — independent deploys + shared packages |
| Single team, single app | No — standard Next.js is simpler |
| Shared component library across apps | Yes — packages/ui with boundary rules |
| Gradual migration from monolith | Yes — extract features into micro-apps incrementally |
| Need version-skew protection | Yes — isolated builds per micro-app |
Turborepo 2.6+ has stable Bun support with granular lockfile analysis:
bun.lock (text format). If only bun.lockb (binary) is found, it errors with a prompt to generate a text lockfile. Generate with bun install --save-text-lockfile.bun.lock to detect which specific packages changed and only invalidates caches for affected tasks — not the entire monorepo.turbo prune works with Bun workspaces, generating a minimal lockfile for single-app deploys.bun.lock changes don't touch a project's dependencies. Combined with --affected, only changed packages and their dependents rebuild.Known issue:
turbo prunewith Bun 1.3+ may produce lockfiles with formatting differences that breakbun i --frozen-lockfile. Track fixes in turborepo#11007.
Vercel auto-detects Turborepo and optimizes builds. Each app in apps/ can be a separate Vercel project with automatic dependency detection.
| Scenario | Use Turborepo? |
|---|---|
| Single Next.js app | No — Turbopack handles bundling |
| Multiple apps sharing code | Yes — orchestrate builds |
| Shared component library | Yes — manage dependencies |
| CI taking too long | Yes — caching + affected |
| Team sharing build artifacts | Yes — remote caching |
| Enforcing architecture boundaries | Yes — boundary rules |
| Complex multi-step CI pipelines | Yes — task graph + matrix |
{
"$schema": "https://turborepo.dev/schema.json",
"globalDependencies": [".env"],
"globalEnv": ["CI", "NODE_ENV"],
"tasks": {
"build": {
"dependsOn": ["^build"],
"outputs": [".next/**", "dist/**"],
"env": ["DATABASE_URL", "NEXT_PUBLIC_API_URL"],
"inputs": ["src/**", "package.json", "tsconfig.json"]
},
"test": {
"dependsOn": ["build"],
"outputs": ["coverage/**"],
"env": ["TEST_DATABASE_URL"]
},
"test:unit": {
"dependsOn": [],
"outputs": ["coverage/**"]
},
"lint": {
"inputs": ["src/**", ".eslintrc.*"]
},
"typecheck": {
"dependsOn": ["^build"],
"inputs": ["src/**", "tsconfig.json"]
},
"db:generate": {
"cache": false
},
"dev": {
"cache": false,
"persistent": true
},
"clean": {
"cache": false
}
}
}# Single package
turbo build --filter=web
# Package and its dependencies
turbo build --filter=web...
# Package and its dependents (what depends on it)
turbo build --filter=...ui
# Multiple packages
turbo build --filter=web --filter=api
# By directory
turbo build --filter=./apps/*
# Packages that changed since main
turbo build --filter=[main]
# Combine: changed packages and their dependents
turbo build --filter=...[main]
# Exclude a package
turbo build --filter=!docs
# Packages matching a pattern
turbo build --filter=@myorg/*name: CI
on: [push, pull_request]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0 # Required for --affected
- uses: actions/setup-node@v4
with:
node-version: 22
- run: npm ci
- run: turbo build test lint --affected
env:
TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
TURBO_TEAM: ${{ vars.TURBO_TEAM }}
deploy-web:
needs: build
if: github.ref == 'refs/heads/main'
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npm ci
- run: turbo build --filter=web
env:
TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
TURBO_TEAM: ${{ vars.TURBO_TEAM }}jobs:
detect:
runs-on: ubuntu-latest
outputs:
packages: ${{ steps.list.outputs.packages }}
steps:
- uses: actions/checkout@v4
- id: list
run: |
PACKAGES=$(turbo ls --affected --output=json | jq -c '[.[].name]')
echo "packages=$PACKAGES" >> "$GITHUB_OUTPUT"
test:
needs: detect
if: needs.detect.outputs.packages != '[]'
runs-on: ubuntu-latest
strategy:
matrix:
package: ${{ fromJson(needs.detect.outputs.packages) }}
steps:
- uses: actions/checkout@v4
- run: npm ci
- run: turbo test --filter=${{ matrix.package }}# Set in CI environment
TURBO_TOKEN=your-vercel-token
TURBO_TEAM=your-vercel-team
# Builds automatically use remote cache
turbo build# Watch a specific task
turbo watch test
# Watch with a filter
turbo watch test --filter=web
# Watch multiple tasks
turbo watch test lint{
"boundaries": {
"tags": {
"apps/*": ["app"],
"packages/ui": ["shared", "ui"],
"packages/utils": ["shared"],
"packages/config": ["config"]
},
"rules": [
{
"from": ["app"],
"allow": ["shared"]
},
{
"from": ["shared"],
"deny": ["app"]
}
]
}
}# Check boundary compliance
turbo boundaries
# Add to your pipeline
{
"tasks": {
"check": {
"dependsOn": ["lint", "typecheck", "boundaries"]
},
"boundaries": {}
}
}# Print graph to terminal
turbo build --graph
# Output as DOT format (Graphviz)
turbo build --graph=graph.dot
# Output as JSON
turbo build --graph=graph.json
# Open interactive graph in browser
turbo build --graph=graph.html# Show tasks that would run without executing them
turbo build --dry-run
# JSON output for programmatic use
turbo build --dry-run=json# Visual package/task graph explorer (hot-reloads on changes)
turbo devtools
# Search Turborepo docs from the terminal (returns agent-friendly markdown)
turbo docs
# Upgrade to latest Turborepo
npx @turbo/codemod migrate// packages/ui/turbo.json
{
"extends": ["@myorg/config"],
"tasks": {
"build": {
"outputs": ["dist/**"]
}
}
}# Run build across all packages
turbo build
# Run only affected packages (changed since main branch)
turbo build --affected
# Run specific tasks in specific packages
turbo build --filter=web
# Run with remote caching
turbo build --remote-cache
# Prune monorepo for a single app deployment
turbo prune web --docker
# List all packages
turbo ls
# List affected packages
turbo ls --affected# Login to Vercel for remote caching
turbo login
# Link to a Vercel team
turbo link
# Now builds share cache across all machines
turbo build # Cache hits from CI, teammates, etc.my-monorepo/
├── turbo.json
├── package.json
├── apps/
│ ├── web/ # Next.js app
│ │ └── package.json
│ ├── api/ # Backend service
│ │ └── package.json
│ └── docs/ # Documentation site
│ └── package.json
├── packages/
│ ├── ui/ # Shared component library
│ │ └── package.json
│ ├── config/ # Shared configs (eslint, tsconfig)
│ │ └── package.json
│ └── utils/ # Shared utilities
│ └── package.json
└── node_modules/# Only build/test packages that changed since main
turbo build test lint --affectedmy-platform/
├── turbo.json
├── package.json
├── apps/
│ ├── shell/ # Layout / shell app (owns top-level routing)
│ ├── dashboard/ # Micro-app: dashboard features
│ ├── settings/ # Micro-app: settings features
│ └── marketing/ # Micro-app: public marketing site
└── packages/
├── ui/ # Shared component library
├── auth/ # Shared auth utilities
└── config/ # Shared tsconfig, eslint# Deploy only the dashboard micro-app
turbo build --filter=dashboard
# Deploy all micro-apps in parallel
turbo build --filter=./apps/*
# Deploy only micro-apps that changed since main
turbo build --filter=./apps/*...[main]{
"tasks": {
"build": {
"dependsOn": ["^build"],
"outputs": [".next/**", "dist/**"]
}
}
}// apps/shell/next.config.ts
import type { NextConfig } from 'next'
const nextConfig: NextConfig = {
async rewrites() {
return [
{ source: '/dashboard/:path*', destination: 'https://dashboard.example.com/dashboard/:path*' },
{ source: '/settings/:path*', destination: 'https://settings.example.com/settings/:path*' },
]
},
}
export default nextConfig{
"boundaries": {
"tags": {
"apps/*": ["micro-app"],
"packages/ui": ["shared"],
"packages/auth": ["shared"]
},
"rules": [
{ "from": ["micro-app"], "allow": ["shared"] },
{ "from": ["shared"], "deny": ["micro-app"] }
]
}
}# Ensure text lockfile for Turborepo compatibility
bun install --save-text-lockfile
# Run only affected packages (works with Bun lockfile detection)
turbo build --affected