Monorepo
This guide walks through the complete setup of a TypeScript monorepo using Moon.build from scratch — pnpm workspaces, shared tsconfig, Vitest per package, Moon task orchestration, and a GitHub Actions CI pipeline with remote caching. Estimated setup time: 45 minutes. Key Takeaways 1. Moon requires explicit project registration and task
Monorepo
Combining Moon.build with Vitest gives you fast, isolated test runs per package with smart caching, plus the option of a unified workspace-level test runner for coverage merging. Moon handles the orchestration; Vitest handles the execution. Key Takeaways 1. Vitest's workspace feature lets you define per-package test environments
Monorepo
Moon, Nx, and Turborepo all solve the "run only what changed" problem in monorepos, but they take different approaches. Moon prioritizes language agnosticism and explicit configuration; Nx leans on its plugin ecosystem and IDE integration; Turborepo optimizes for minimal configuration and zero-friction adoption. Your choice depends on team
Monorepo
Moonrepo's CI performance comes from three compounding optimizations: content-addressed local caching, parallel task execution across dependency levels, and remote caching shared across all runners and branches. Together, they can reduce CI times by 70–90% in large monorepos. Key Takeaways 1. Moon's cache key is a
Monorepo
Moon.build (Moonrepo) is a task runner and monorepo management tool that tracks project dependencies, detects which projects are affected by a change, and runs only the tests that matter — drastically cutting CI time in large codebases. Key Takeaways 1. Moon uses a dependency graph to determine which projects are
Testing
Bun workspaces let you run tests across every package in a monorepo with a single command. Cross-package imports resolve through the workspace protocol, TypeScript paths work without a build step, and bun test --filter targets packages by name pattern — making the monorepo test loop almost as fast as a single-package
Monorepo
Turborepo is Vercel's high-performance build system for JavaScript and TypeScript monorepos. Its core value for testing is the same as for builds: never do the same work twice. With remote caching, a test that passed on your colleague's machine won't re-run in CI — the
Monorepo
pnpm workspaces provide a lightweight monorepo solution built into the pnpm package manager. Unlike Nx or Turborepo, pnpm workspaces have no build graph awareness or caching — they give you the foundation to run commands across packages, and you layer tooling on top. Understanding how to run tests across packages, share
Monorepo
As a monorepo grows, test code starts to duplicate. Every package writes its own createUser() factory, defines its own API mock handlers, and copies the same Jest setup file. A change to the User type means updating factories in five packages. A new API endpoint means updating mocks scattered across
Monorepo
Nx is one of the most popular monorepo build systems for JavaScript and TypeScript projects. Its key promise for testing is simple: only run tests for code that actually changed. When a monorepo contains dozens of applications and libraries, that promise can cut CI time from 45 minutes to under
Monorepo
Bazel is Google's open-source build system, designed from the ground up for very large monorepos. It powers testing at companies where a single repository contains millions of lines of code across dozens of languages. Its approach to testing is fundamentally different from other tools: Bazel treats tests as
Monorepo
The most common CI problem in monorepos is running too many tests on every commit. A change to a CSS file triggers a full backend test suite. An API schema update re-runs E2E tests for three unrelated apps. Over time, CI becomes a 45-minute wall that developers learn to ignore.