Turborepo: Build System for JavaScript & TypeScript Monorepos

What It Is

Turborepo is Vercel’s open-source build system, rewritten in Rust, designed for JavaScript and TypeScript monorepos. It replaces the Node.js-based v1 with a faster, more reliable engine that handles parallel task execution, dependency graph traversal, and remote caching out of the box.

If you work in a monorepo with multiple apps and packages (Next.js, NestJS, React Native, shared UI libraries), Turborepo is the orchestration layer that makes sure your builds run in the right order, skip unchanged work, and finish as fast as possible.

What Makes It Different

The v2 rewrite in Rust is the headline change. The original Turborepo was Node.js-based and struggled with large dependency graphs — cold starts were slow, and memory usage spiked on repos with hundreds of packages. The Rust version (turbo binary, single file) starts in under 100ms and handles dependency graphs at compile time rather than walking them at runtime.

Remote caching is the killer feature. Once you connect it to Vercel Remote Caching (or your own S3-compatible storage), the second CI pipeline gets the same packages built by the first one. No redundant tsc --noEmit or vitest runs. In practice, teams report CI time drops from 20+ minutes to under 3 minutes.

Task dependency inference is smarter in v2. You no longer need to manually wire up dependsOn for every task — Turborepo reads your turbo.json topology and figures out the execution graph automatically.

Who It’s For

Turborepo is for any team running a JavaScript or TypeScript monorepo — whether it’s a Next.js app with a shared UI library, a micro-frontend architecture, or a full-stack project with backend + frontend + mobile. If you have more than 3 packages, the overhead of setting up turbo.json pays for itself within a week.

Real Talk

I set up Turborepo v2 on a monorepo with 12 packages: a Next.js frontend, a NestJS API, a shared UI library, three database packages, and various tooling configs. The migration from v1 was straightforward — npx @turbo/codemod migrate handled most of the boilerplate, and the new turbo.json schema is cleaner.

The first build was actually slower than v1 because Rust’s cold cache isn’t warm yet — but from the second build onward, everything was noticeably faster. The turbo build --filter=web command starts in under a second and finishes in 12 seconds vs. 45 seconds under v1.

The one gotcha: TypeScript project references. Turborepo v2 handles them better than v1, but you still need to configure references in your tsconfig.json manually. Turborepo won’t fix a broken TypeScript setup for you.

Bottom Line

Turborepo is the standard build orchestrator for JS/TS monorepos. The Rust rewrite makes it faster, the remote caching makes CI bearable, and the configuration is simpler than ever. If you’re running a monorepo without it, you’re leaving build time on the table.