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
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
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
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
Monorepo
Turborepo's core promise is simple: run tasks in the order they need to run, skip work you've already done, and do as much in parallel as possible. For testing, this translates to a system where only the packages affected by your changes get tested, previously-passing
Monorepo
pnpm workspaces give you a fast, disk-efficient monorepo foundation, but the testing story requires deliberate setup. Out of the box, you can run pnpm --filter <package> test to execute tests in a specific package, but that's only the beginning. The real value comes from shared
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
Running your full test suite on every commit stops being practical the moment your monorepo grows beyond a handful of packages. When you have 40 applications and 80 shared libraries, waiting 45 minutes for unrelated tests to pass is a tax on every engineer's time. Nx solves this
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
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