Simplifying Dart Mono-repo Management for Efficient Code Sharing and Collaboration
summary
Compares concrete tools and trade offs for Dart mono‑repos, arguing you need tooling for Melos style package overrides, local and distributed caching, and dependency graph visualization. Demonstrates Melos running on Flame and FlutterFire, shows scripts and a graph generator, and claims Melos solves path override headaches while Bazel is powerful but complex. Emphasizes detecting affected packages, partial clones, selective CI runs, and versioning mechanics so changes only build and test what actually depends on them.
AI-written summary · about
chapters (11)
- 0:00Introduction to mono repos
- 1:06Mono vs poly repos explained
- 4:45Conway's law and team structure
- 7:35Advantages of mono repos
- 8:40Disadvantages of mono repos
- 11:07Tools for mono repo management
- 12:10Key features of mono repo tools
- 16:09Modularizing applications
- 18:38Introducing Melos tool
- 19:42Melos demo and features
- 21:53Summary and Q&A
related talks
16mManaging multiple packages in a monorepo
06mHow I Learned to Stop Worrying and Love the Mono Repo
35mThe Gentle Monorepo - Ship Faster and Collaborate Better
31mMonoRepos for the Masses
24mBuilding your ideal codebase: monorepos & multirepos living in harmony
19mEscaping Chaos: Strategies to Move from Polyrepo to Monorepo
21mGit submodules: we have monorepo at home
29mMonorepos, are they right for you?