Avoid Dependency Hell in Flutter Monorepo - Archipelago Flutter Toolkit
20 packages, 3 different versions of flutter_bloc. Pub resolution fails on every other PR.
Centralized dependency management: define versions once, every package stays in sync.
Dependency version conflicts are the number one source of broken builds in Flutter monorepos. Package A uses flutter_bloc 8.1, Package B uses 8.0, and pub resolution fails with a wall of red text. Centralized dependency management solves this: define your dependency versions in one canonical location, then propagate them to all packages automatically. Conflicts are caught before CI, not during. Archipelago generates this tooling into your project's devtools/ directory.
What you get:
Single source of truth for all dependency versions
Automatic propagation to all packages in the monorepo
Version conflict detection before CI runs
Generated into devtools/ (no external dependency)
Works with pub's resolution system
---
Get started:
Website: https://archipelago.banuacoder.com
Install CLI: dart pub global activate archipelago_cli
GitHub: https://github.com/banua-coder/archip...
Discord: / discord
Timestamps:
0:00 Intro
0:05 The version conflict problem
0:15 Centralized dependency definitions
0:30 Automatic propagation
0:45 Conflicts caught early
#flutter #flutterdev #dart #monorepo #mobiledev #archipelago #dependencies #pubdev