Monorepo — Explained with Examples

A monorepo is a single repository containing multiple distinct projects or packages, sharing tooling and versioning under one roof.

Monorepo (monolithic repository) stores code for several projects — libraries, services, frontends, documentation — in one Git repository. This contrasts with polyrepo (many repositories, each for one project). Tools like Nx, Turborepo, Bazel, and Lerna manage monorepo workflows, enabling dependency sharing, unified builds, and atomic cross-project changes.

Think of a monorepo like a department store. Instead of visiting separate shops (polyrepo) for shoes, electronics, and groceries, you go to one building. The inventory (code) is organized by department (directory), checkout is unified (shared CI), and you can move between departments instantly (cross-project refactoring).

Monorepo advantages include simplified dependency management, consistent tooling, atomic commits across packages, and easier code sharing. Tradeoffs include larger clone sizes, more complex CI pipelines, and potential permission management challenges.

my-monorepo/
├── packages/
│   ├── ui/          # Shared UI component library
│   ├── api/         # Backend API service
│   ├── web/         # Main web application
│   └── mobile/     # Mobile app (React Native)
├── tools/           # Build and dev tooling
├── package.json     # Root workspace config
├── nx.json          # Nx workspace config
└── tsconfig.json    # Shared TypeScript config

Tech giants like Google, Meta, and Microsoft use monorepos. For smaller teams, monorepo tools have matured significantly, making this approach viable without custom infrastructure.

Git, CI/CD, Bundling, npm

Build Tools Overview