Monorepo tooling — Turborepo, Nx, and workspace management

Managing multiple related packages in separate repos leads to version drift, duplicated tooling, and difficult cross-package changes. Need a monorepo setup with efficient builds and dependency management.

(1) Package manager workspaces: npm/pnpm/yarn workspaces for dependency hoisting and cross-package linking. pnpm is recommended — strict dependency isolation. (2) Turborepo: build orchestration with task caching. Defines task dependencies in turbo.json. Remote caching shares build results across CI and team. (3) Nx: full-featured monorepo tool with affected detection (only rebuild changed packages and dependents). Best for large orgs. (4) Structure: packages/ for libraries, apps/ for applications. (5) Shared configs: one tsconfig, eslint, prettier config at root. (6) Versioning: changesets for version management and changelogs. (7) CI: use affected/changed detection to only test and build what changed.

Monorepos enable atomic changes across packages, shared tooling, and consistent versioning. Build tools like Turborepo make them scalable by caching and parallelizing task execution.