finds.dev← search

// the find

gqty-dev/gqty

★ 1,035 · TypeScript · MIT · updated Jun 2026

The No-GraphQL Client for TypeScript

gqty is a GraphQL client for TypeScript that eliminates hand-written query strings by inferring data requirements from how you access properties at runtime using Proxies. It generates a typed client from your schema, then tracks field accesses during render to build and batch GraphQL queries automatically. The target audience is TypeScript-heavy React teams who are tired of maintaining query files.

The proxy-based field tracking is genuinely clever — you write `user.name` and it figures out the query, which removes an entire class of query/component drift bugs. Type errors propagate directly from schema changes to call sites without a separate codegen+validate step, which is faster feedback than Apollo or urql. The cache layer supports normalization, persistence, and SSR prepass, and the React package covers most real-world patterns (lazy, paginated, subscriptions, HOC). SolidJS support is a nice differentiator most GraphQL clients don't bother with.

1,035 stars and 34 forks after years of development signals weak adoption — Apollo and urql have solved this problem space for most teams, and gqty's magic-proxy approach has a steeper mental model when something goes wrong. The runtime field tracking means you can silently under-fetch if you conditionally access fields outside the reactive scope; this is a real footgun that's hard to debug. The repo has a `compat/` layer suggesting significant breaking changes in its history, and the examples are all using Next.js pages router — no App Router examples, which is where new projects are. Solid support appears to have a single test file and no CHANGELOG, suggesting it's not production-ready.

View on GitHub → Homepage ↗

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →