--- name: turborepo-c8dc2c4c4ab7 description: >- Turborepo is a build system for JavaScript/TypeScript monorepos that caches task outputs and runs tasks in dependency order. Use when configuring build pipelines, setting up caching, pruning workspaces for Docker, or optimizing CI/CD for monorepo projects. Trigger words: turborepo, turbo, monorepo, pipeline, workspace, remote cache, turbo.json. license: Apache-2.0 compatibility: "Requires a current Node.js LTS with npm, yarn, pnpm or bun workspaces" metadata: author: terminal-skills version: "1.1.0" repository: "https://github.com/vercel/turborepo" category: development tags: "turborepo, monorepo, build-system, caching, ci-cd" --- # Turborepo ## Overview Turborepo is a high-performance build system for JavaScript/TypeScript monorepos that intelligently caches task outputs, parallelizes execution across CPU cores, and ensures teams only rebuild what has changed. It integrates with npm, yarn, and pnpm workspaces. ## Instructions - Install `turbo` as a root devDependency (`npm install turbo --save-dev`, or the pnpm/yarn/bun equivalent) and run it through the package manager. Turborepo 2.x needs a `packageManager` field in the root `package.json` and a workspace definition (`workspaces`, or `pnpm-workspace.yaml`). - Define tasks under the `tasks` key of `turbo.json` (it was called `pipeline` in 1.x; `npx @turbo/codemod migrate` upgrades old repos). Use `dependsOn` for ordering, the `^` prefix for the same task in dependencies (`"dependsOn": ["^build"]`), and `outputs` for cacheable artifacts (`["dist/**", ".next/**", "!.next/cache/**"]`). - Run tasks with `turbo run build lint` (or `turbo build`). Add `--ui=stream` for plain log output in CI. Mark long-running tasks `"cache": false, "persistent": true`. - Caching: the hash covers the package's files, its dependencies' hashes, the task's `inputs` (default: all git-tracked files in the package) and declared environment variables. Declare variables in a task's `env` (or root `globalEnv`). Task `env` mode is `strict` by default: undeclared variables are not passed to the task, so list runtime-only secrets in `passThroughEnv` rather than `env` if they should not affect the hash. - Filtering: `--filter=@shop/web` for one package, `--filter=@shop/web...` for it plus its dependencies, `--filter='...[origin/main]'` for packages changed since a git ref, or `--affected` for packages changed against `main` (and their dependents). `turbo ls` lists packages; `turbo run build --graph=graph.mermaid` writes the task graph; `--dry=json` shows what would run and the hashes. - Docker: `turbo prune @shop/web --docker` writes `out/json` (package.json files and pruned lockfile, for the install layer), `out/full` (sources) and the lockfile. Copy `out/json/` first, install, then copy `out/full/` and build. The `--scope` flag no longer exists; pass the package name as an argument. Add a `.dockerignore` with `node_modules`. - Remote Cache: `npx turbo login` then `npx turbo link` for the Vercel Remote Cache (free on all plans). In CI, set `TURBO_TOKEN` and `TURBO_TEAM` instead. Set `"remoteCache": {"signature": true}` plus `TURBO_REMOTE_CACHE_SIGNATURE_KEY` to sign artifacts. Self-hosted caches implement the documented Remote Cache API and are selected with `TURBO_API`. - Shared packages: create focused internal packages (`@repo/ui`, `@repo/db`) with shared `tsconfig` and ESLint config packages; `turbo generate` scaffolds a new app or package. ## Examples ### Example 1: Set up a monorepo with a web app and a shared UI package **User request:** "Initialize a monorepo with a Next.js app and shared UI library, with caching" Root `package.json` and `turbo.json`: ```json { "name": "shop", "private": true, "packageManager": "pnpm@10.18.0", "devDependencies": { "turbo": "^2.11.10" } } ``` ```json { "$schema": "https://turborepo.dev/schema.json", "tasks": { "build": { "dependsOn": ["^build"], "outputs": [".next/**", "!.next/cache/**", "dist/**"], "env": ["NEXT_PUBLIC_API_URL"] }, "lint": {}, "dev": { "cache": false, "persistent": true } } } ``` With `pnpm-workspace.yaml` listing `apps/*` and `packages/*` (`apps/web` named `@shop/web`, `packages/ui` named `@shop/ui`), run `pnpm turbo run build`. The first run prints `cache miss, executing`; an immediate second run prints `cache hit, replaying logs` for both packages and ends with `FULL TURBO`. Changing `NEXT_PUBLIC_API_URL` produces a miss again because it is declared in `env`. ### Example 2: Build one service into a small Docker image **User request:** "Create a Dockerfile for deploying @shop/api from our Turborepo monorepo" ```console $ npx turbo prune @shop/api --docker Generating pruned monorepo for @shop/api in ./out - Added @shop/api - Added @shop/db ``` ```dockerfile FROM node:24-slim AS base RUN corepack enable WORKDIR /app FROM base AS pruner COPY . . RUN npx turbo@2 prune @shop/api --docker FROM base AS build COPY --from=pruner /app/out/json/ . RUN pnpm install --frozen-lockfile COPY --from=pruner /app/out/full/ . RUN pnpm turbo run build --filter=@shop/api CMD ["node", "apps/api/dist/server.js"] ``` The install layer is reused until a `package.json` or the lockfile changes, and the image holds only `@shop/api` and `@shop/db`. Pass `TURBO_TOKEN` and `TURBO_TEAM` as build secrets if the build should use the Remote Cache. ## Guidelines - Always declare `outputs` for tasks that produce files; a task with no `outputs` caches only its logs. Exclude framework caches such as `!.next/cache/**`. - Declare every environment variable that changes build output in `env` or `globalEnv`; forgetting one gives stale cache hits, and `strict` mode hides undeclared variables from the task. - Use `^build` in `dependsOn` when a task consumes dependencies' build output; use a plain name (`"dependsOn": ["build"]`) for same-package ordering. - Run `turbo` from the repository root, and commit the lockfile: it is part of the hash and `turbo prune` needs it. - Never copy the whole monorepo into an image; use `turbo prune --docker`. - Keep tokens (`TURBO_TOKEN`) in CI secrets, not in `turbo.json` or the repository. Enable signature verification when the cache is shared with less trusted contributors. - Turborepo orchestrates scripts; it does not replace a bundler or a package manager. For a single-package repository it adds little. --- Source attribution: terminal-skills Original project: https://github.com/TerminalSkills/skills/blob/8a9852d489f274538be9bf1c9121aeb403750b1c/skills/turborepo/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Dave AI. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS Copyright 2025 Terminal Skills Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Dave AI resource metadata Creator / publisher: terminal-skills Original project: https://github.com/TerminalSkills/skills/blob/8a9852d489f274538be9bf1c9121aeb403750b1c/skills/turborepo/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Product Management Roles: Frontend Developer, Backend Developer, DevOps / SRE, Full-Stack Developer, Product Manager Specialties: DevOps, Backend Tools: Node.Js, Npm, Yarn, Pnpm Country applicability: Country not specified Classification basis: Source category, role and specialization labels Instruction SHA-256: a9b5d2409c3081a98483cc46f26decefe7d56d642e305664b195470c588eb903