analyze-overfetch

To identify unused fields in GraphQL queries, you inventory queries and fragments across the codebase, trace how fetched fields are consumed by client-side components, and generate a catalog of over-fetched data. This reveals fields safe for removal.

GraphQL over-fetching occurs when queries retrieve more data than the application consumes. Auditing involves inventorying artifacts, tracing field usage in consumers, and generating an audit-ready plan with recommendations for safe removals or per-consumer query splits.

Optimizing shared GraphQL fragments in a large codebase requires tracing field usage across multiple routes and consumers. The process inventories artifacts and generates trace reports to inform safe removals and per-consumer query splits, minimizing data transfer.

Yes, you can prepare a migration plan when refactoring APIs that introduce extra fields. The audit generates trace reports of field usage and outputs an audit-ready plan for safe optimizations, ensuring unused fields are removed before migration.

The best way to split GraphQL queries for per-consumer usage is to generate a catalog of fetched fields and trace their actual usage. This analysis informs safe per-consumer query splits, removing unused fields from common queries and fragments.

Yes, this overfetch analysis is designed for large codebases with client-side GraphQL usage. It inventories queries and fragments, traces field usage across multiple routes, and outputs an audit-ready plan for safe optimizations.