Open source · GraphQL
dartpollo
A Dart GraphQL client and code-generation ecosystem built from a heavily modified Artemis fork and used in production.
- Role
- Creator and maintainer
- Period
- 2025 — Present
01
The challenge
An unmaintained GraphQL dependency made a critical mobile data layer harder to evolve, support, and keep aligned with current tooling.
02
My contribution
I forked Artemis, heavily modified the client and generator, organized the work as a Melos monorepo, and maintain its release automation and compatibility fixes.
03
The outcome
The resulting three-package ecosystem is published on pub.dev and became a maintainable, inspectable foundation for a production GraphQL migration.
How I approached it
I treated the fork as a product rather than a one-off patch. The repository separates the runtime client, generator, and shared annotations while keeping releases coordinated in one monorepo.
Maintenance includes dry-run publishing checks, changelogs, OIDC-based publishing, and practical dependency fixes when real consumers find compatibility problems.
Technology
Tools that supported the work
Verify the work