System Design · Middle · Question 34 of 75
What are the pros and cons of a monorepo for several frontend apps?
- ✓Correct answer: Shared code and atomic changes, but you need build and caching tooling
- 2A monorepo makes users' browsers run faster
- 3A monorepo forbids different dependency versions and any libraries
Explanation
A change to the UI kit and all apps can be done in one PR, and code reuse is easier. The cost is scaling CI: you need tools with a dependency graph and caching (Turborepo, Nx), plus ownership and boundary rules.