// the find
BetterTyped/hyper-fetch
⚡ Fetching and realtime data exchange framework.
HyperFetch is a TypeScript data-fetching framework that tries to be a single abstraction over REST, GraphQL, WebSockets, SSE, and Firebase. It adds caching, request queuing, deduplication, and offline support on top, with a builder-style API for defining typed requests. Aimed at TypeScript-heavy frontend teams who want one mental model instead of axios + tanstack-query + socket.io.
The end-to-end type inference is genuinely well done — you define the response shape once on the request and it flows through hooks, cache, and error states without casting. The adapter system is a real architectural win: swapping from fetch to axios or adding a Firebase adapter doesn't change call-site code. The OpenAPI CLI code generator is practical and saves the usual hand-maintenance of typed SDK wrappers. DevTools plugin for inspecting cache and queues in-browser is the kind of thing most teams build themselves and never quite finish.
With only 1.3k stars and 32 forks after what looks like several years of development, adoption is thin — that means sparse Stack Overflow answers, fewer battle-tested bug reports, and real migration risk if the maintainers lose interest. The 'one interface for everything' claim is where abstractions usually leak: WebSocket and SSE semantics are fundamentally different from request/response, and forcing them through the same API surface tends to produce awkward workarounds once you hit edge cases. The package count (core, react, sockets, firebase, firebase-admin, graphql, axios, devtools, cli) is a maintenance surface that a small team will struggle to keep in sync across major versions — v7 and v8 released within the same year suggests churn. No mention of bundle-splitting story if you only need REST.