Managing multiple packages in a monorepo
summary
Monorepo management for Dart/Flutter becomes a one‑tool workflow: Melos links local packages, fixes lockfiles or uses pubspec_overrides, and removes the manual path‑dependency dance that broke builds. Example repo has ~30 packages; commands used are melos bootstrap to link and get, melos version to bump versions automatically from Conventional Commits and generate changelogs, and melos publish to push many packages to pub.dev at once. Manual version overrides are supported via a flag.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:49Problem with multiple packages
- 3:22What is a monorepo
- 4:51Monorepo pros and cons
- 5:54What is Melos
- 7:41Semantic versioning basics
- 8:25Conventional commits explained
- 9:06Automatic changelog generation
- 9:28Melos bootstrap and versioning
- 10:13Publishing packages with Melos
- 11:15Manual versioning control
- 11:59Running scripts across packages
- 13:51Missing Melos features
- 15:14Alternatives to monorepo
related talks
19mEscaping Chaos: Strategies to Move from Polyrepo to Monorepo
29mMonorepos, are they right for you?
24mBuilding your ideal codebase: monorepos & multirepos living in harmony
31mMonoRepos for the Masses
20mBuilding with Monorepos
46mExploring the power of monorepos: When and why to use them
06mHow I Learned to Stop Worrying and Love the Mono Repo
19mMonorepos: Any Size Fits All