Exploring the power of monorepos: When and why to use them
summary
Claim: moving related projects into a single repo cuts maintenance, enforces one-version dependency management, and simplifies CI/CD by sharing configs and rules. Demonstration uses an NX workspace to create apps and two local libraries, shows local library linking so fixes don’t require npm publishes, and runs tests in parallel with incremental remote cache to skip unchanged builds. Tools mentioned: npm workspaces, Lerna, Bazel, Turborepo, Rush; the NX demo initializes, builds and successfully serves apps.
AI-written summary · about
related talks
19mKeynote: Why Monorepos
24mBuilding your ideal codebase: monorepos & multirepos living in harmony
29mUnderstanding Monorepos: What you need to know
01h 03mMonorepo – How to do frontend faster, better and safer
31mMonoRepos for the Masses
41mHandling Monorepos Today
29mMonorepos, are they right for you?
19mKeynote: Why Monorepos