Semantic Coherence: Turborepo – Signal Evidence & AI Readability

Skip to contentIntroductionGetting startedInstallationStart with an exampleAdd to an existing repositoryEditor integrationCrafting your repositoryAPI referenceCore conceptsGuidesCommunitySupport policyGlossaryChangelog
[H1] Make ship happen
Turborepo is the build system for JavaScript and TypeScript codebases9,001,168hours of compute savedGet started$ npm i turbo
[H2] Scale your workflows
Optimize your local and CI tasks to save years of engineering time and compute.
[H3] Works with any provider
Integrate with any CI provider for speed at all scales
[H3] Remote Caching
Never do the same work twice
[H3] Effortless monorepos
Easily define your workflows for local development and CI
[H2] Simple setup
Start a new repository or migrate an existing repo incrementally in minutes.Read the docs{ "tasks": { "build": { "dependsOn": ["^build"] } }}Declaring a build task# Login to Remote Cacheturbo login# Link to Remote Cacheturbo link# Run tasksturbo run buildLinking to Remote Cache and running tasks
[H2] What builders say about Turborepo
[IMG: Matt Pocock]
Matt Pocock@mattpocockuk? @turborepo saved us 67 HOURS of CI since we adopted it.That's a team of only 4 full-time devs at @statelyai. Nuts.
[IMG: Lewis ⚡]
Lewis ⚡@lewisbuildsaiIf turborepo has a million fans, then I am one of them. If turborepo has ten fans, then I am one of them. If turborepo has only one fan then that is me. If turborepo has no fans, then that means I am no longer on earth. If the world is against turborepo, then I am against the world.
[IMG: Cory House]
Cory House@housecorI'm really enjoying @turborepo. It's a game changer.With Turbo, I have an incentive to break my repo down into many small, focused packages. This way, Turbo can cache each little build. So when I hit save, only the package I changed needs to recompile.Really speeds things up!
[IMG: Shrey Gupta]
Shrey Gupta@shreygupswait i kinda love turborepo
[IMG: Jono Alford]
Jono Alford@jonoalfordThe second we started using this for monorepos is the second we stopped having to worry about using monorepos.
[IMG: ALIAS]
ALIASLoadingALIASTurborepo is the best.
[IMG: Andrew Lisowski]
Andrew Lisowski@HipsterSmoothieJust setting up @turborepo in @DescriptApp's front-end cut our bill in half and saved us $20k
[IMG: Pontus Abrahamsson]
Pontus Abrahamsson@pontusabI love a monorepo setup, having everything in one place powered by Turborepo ?
[H2] Deploy your Turborepo today.
Get started$ npm i turbo

Skip to contentIntroductionGetting startedInstallationStart with an exampleAdd to an existing repositoryEditor integrationCrafting your repositoryAPI referenceCore conceptsGuidesCommunitySupport policyGlossaryChangelog
[H1] Introduction
Welcome to the Turborepo documentation!
[H2] What is Turborepo?
Turborepo is a high-performance build system for JavaScript and TypeScript codebases. It is designed for scaling monorepos and also makes workflows in single-package workspaces faster, too.
From individual developers to the largest enterprise engineering organizations in the world, Turborepo is saving years of engineering time and millions of dollars in compute costs through a lightweight approach to optimizing the tasks you need to run in your repository.
[H2] The monorepo problem
Monorepos have many advantages - but they struggle to scale. Each workspace has its own test suite, its own linting, and its own build process. A single monorepo might have thousands of tasks to execute.
[IMG: A representation of a typical monorepo. The first application took 110 seconds to complete its tasks. The second application took 140 seconds to complete its tasks. The shared package between them took 90 seconds to complete its tasks.]
These slowdowns can dramatically affect the way your teams build software, especially at scale. Feedback loops need to be fast so developers can deliver high-quality code quickly.
[H2] The monorepo solution
[IMG: The monorepo from before using Turborepo, showing how it can hit cache to complete tasks for all three packages in 80 milliseconds.]
Turborepo solves your monorepo's scaling problem. Remote Cache stores the result of all your tasks, meaning that your CI never needs to do the same work twice.
Additionally, task scheduling can be difficult in a monorepo. You may need to build, then test, then lint...
Turborepo schedules your tasks for maximum speed, parallelizing work across all available cores.
Turborepo can be adopted incrementally and you can add it to any repository in just a few minutes. It uses the package.json scripts you've already written, the dependencies you've already declared, and a single turbo.json file. You can use it with any package manager, like npm, yarn or pnpm since Turborepo leans on the conventions of the npm ecosystem.
[H2] How to use these docs
We will do our best to keep jargon to a minimum - but there are some need-to-know words that will be important to understand as you read through the docs. We've created a glossary page to help you out in case you're learning about these terms.
[H2] Join the community
If you have questions about anything related to Turborepo, you're always welcome to ask the community on GitHub Discussions, Vercel Community, and Twitter.9,001,168hoursTotal Compute SavedGet started with Remote Caching →
[H3] On this page
What is Turborepo?The monorepo problemThe monorepo solutionHow to use these docsJoin the communityEdit this page on GitHubScroll to topGive feedbackCopy pageAsk AI about this pageOpen in chat

Skip to contentIntroductionGetting startedInstallationStart with an exampleAdd to an existing repositoryEditor integrationCrafting your repositoryAPI referenceCore conceptsGuidesCommunitySupport policyGlossaryChangelog
[H1] Make ship happen
Turborepo is the build system for JavaScript and TypeScript codebases9,001,168hours of compute savedGet started$ npm i turbo
[H2] Scale your workflows
Optimize your local and CI tasks to save years of engineering time and compute.
[H3] Works with any provider
Integrate with any CI provider for speed at all scales
[H3] Remote Caching
Never do the same work twice
[H3] Effortless monorepos
Easily define your workflows for local development and CI
[H2] Simple setup
Start a new repository or migrate an existing repo incrementally in minutes.Read the docs{ "tasks": { "build": { "dependsOn": ["^build"] } }}Declaring a build task# Login to Remote Cacheturbo login# Link to Remote Cacheturbo link# Run tasksturbo run buildLinking to Remote Cache and running tasks
[H2] What builders say about Turborepo
[IMG: Matt Pocock]
Matt Pocock@mattpocockuk? @turborepo saved us 67 HOURS of CI since we adopted it.That's a team of only 4 full-time devs at @statelyai. Nuts.
[IMG: Lewis ⚡]
Lewis ⚡@lewisbuildsaiIf turborepo has a million fans, then I am one of them. If turborepo has ten fans, then I am one of them. If turborepo has only one fan then that is me. If turborepo has no fans, then that means I am no longer on earth. If the world is against turborepo, then I am against the world.
[IMG: Cory House]
Cory House@housecorI'm really enjoying @turborepo. It's a game changer.With Turbo, I have an incentive to break my repo down into many small, focused packages. This way, Turbo can cache each little build. So when I hit save, only the package I changed needs to recompile.Really speeds things up!
[IMG: Shrey Gupta]
Shrey Gupta@shreygupswait i kinda love turborepo
[IMG: Jono Alford]
Jono Alford@jonoalfordThe second we started using this for monorepos is the second we stopped having to worry about using monorepos.
[IMG: ALIAS]
ALIASLoadingALIASTurborepo is the best.
[IMG: Andrew Lisowski]
Andrew Lisowski@HipsterSmoothieJust setting up @turborepo in @DescriptApp's front-end cut our bill in half and saved us $20k
[IMG: Pontus Abrahamsson]
Pontus Abrahamsson@pontusabI love a monorepo setup, having everything in one place powered by Turborepo ?
[H2] Deploy your Turborepo today.
Get started$ npm i turbo

Skip to contentIntroductionGetting startedInstallationStart with an exampleAdd to an existing repositoryEditor integrationCrafting your repositoryAPI referenceCore conceptsGuidesCommunitySupport policyGlossaryChangelog
[H1] Getting started
Get started with Turborepo.If you're new to Turborepo, you can follow these steps to get started.
[H2] Install Turborepo
Install turbo globally so you can conveniently run turbo commands in your terminal from anywhere in your repository.npmyarnpnpmnpm install turbo --globalyarn global add turbopnpm add turbo --globalTo learn more about installing turbo, see the installation guide.
[H2] Choose your learning path
[H3] Use create-turbo
Start with a template
[H3] Use an example
Start with a framework-specific example
[H3] Follow the in-depth guides
From zero to monorepo
[H3] Add to an existing repository
Make your current repo fast9,001,168hoursTotal Compute SavedGet started with Remote Caching →
[H3] On this page
Install TurborepoChoose your learning pathEdit this page on GitHubScroll to topGive feedbackCopy pageAsk AI about this pageOpen in chat