Understanding Monorepos: What you need to know
summary
Monorepos work by turning many projects into isolated units with project graph metadata so tooling knows exact dependencies, enforces module boundaries via tags and ESLint, and flags imports outside a lib’s public API (index.ts). Nx runs only impacted tasks with the affected command, uses per-project targets and generators to create consistent apps/libs, and caches results so builds/tests are fetched from remote caching instead of rerunning. Example: change a design-system component and run apps immediately without publishing.
AI-written summary · about
chapters (9)
- 0:00Introduction to monorepos
- 3:01Defining monorepos and relationships
- 7:20Polyrepos vs monorepos
- 11:13Monorepos for collaboration
- 13:23Misconceptions about monorepos
- 16:09NX tooling for monorepos
- 21:02Project targets and caching
- 24:33Atomic changes with NX
- 27:24Key takeaways and resources
related talks
19mMonorepos: Any Size Fits All
46mExploring the power of monorepos: When and why to use them
31mThe monorepo: self-organising codebases and automatic scaling
45mMonorepos - The Benefits, Challenges and Importance of Tooling Support
24mBuilding Fast, Maintainable JavaScript Monorepos with Nx
19mKeynote: Why Monorepos
01h 03mMonorepo – How to do frontend faster, better and safer
21mFast React Monorepos with High Quality DX