monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
By wshobson · 13,131 installs
npx skills add wshobson/agents --skill monorepo-management
Source repository · Upstream listing
Monorepo Management
Build efficient, scalable monorepos that enable code sharing, consistent tooling, and atomic changes across multiple packages and applications.
When to Use This Skill
Setting up new monorepo projects
Migrating from multi repo to monorepo
Optimizing build and test performance
Managing shared dependencies
Implementing code sharing strategies
Setting up CI/CD for monorepos
Versioning and publishing packages
Debugging monorepo specific issues
Core Concepts
1. Why Monorepos?
Advantages:
Shared code and dependencies
Atomic commits across projects
Consistent tooling and standards
Easier refactoring
Simplified dependency management
Better code visibility
Challenges:
Build performance at scale
CI/CD complexity
Access control
Large Git repository
2. Monorepo Tools
Package Managers:
pnpm workspaces (recommended)
npm workspaces
Yarn workspaces
Build Systems:
Turborepo (recommended for most)
Nx (feature rich, complex)
Lerna (older, maintenance mode)
Turborepo Setup
Initial Setup
Configuration
Package Structure
Detailed patterns and worked examples
Detailed pattern documentation lives in references/details.md . Read that file when the navigation tier above is insufficient.
Best Practices
1. Consistent Versioning : Lock dependency versions across workspace
2. Shared Configs : Centralize ESLint, TypeScript, Prettier configs
3. Dependency Graph : Keep it acyclic, avoid circular dependencies
4. Cache Effectively : Configure inputs/outputs correctly
5. Type Safety : Share types between frontend/backend
6. Testing Strategy : Unit tests in packages, E2E in apps
7. Documentation : README in each package
8. Release Strategy : Use changesets for versioning
Common Pitfalls
Circular Dependencies : A depends on B, B depends on A
Phantom Dependencies : Using deps not in package.json
Incorrect Cache Inputs : Missing files in Turborepo inputs
Over Sharing : Sharing code that should be separate
Under Sharing : Duplicating code across packages
Large Monorepos : Without proper tooling, builds slow down
Publishing Packages