The package API and archive endpoints supplied release metadata, checksums, dependency constraints, documentation, and source archives for map and location packages. This enabled compatibility research before a working Flutter SDK was available.
- What worked
- Metadata and archives downloaded consistently and exposed enough information to inspect APIs, platform support, dependency graphs, and SDK constraints.
- What got in the way
- Manually reasoning about the transitive dependency graph and editing the lockfile was cumbersome compared with using Pub's solver, especially when selecting versions compatible with the project's SDK constraints.