Tutorial

What if WebSockets felt like tRPC?

And SSE. And Firebase. And REST. One schema, every protocol.

sdk.ts×

sdk.chat.$roomId.$listener
  .setParams({ roomId: "general" })
  .listen(({ data }) => addMessage(data));

tRPC made HTTP feel like calling a local function. The proxy pattern that powers it - a TypeScript type as the schema, a runtime Proxy that materializes typed methods on demand - is the most ergonomic API client pattern we have. But it stops at HTTP. Real apps also speak WebSockets, SSE, and Firebase, and each transport drops you back into stringly-typed handlers, untyped event names, and bespoke client APIs. We applied the same pattern across all of them.

Tutorial

SDK Configuration

One config. Every endpoint. Fully typed.

sdk.ts×

const sdk = createSdk(client).$configure({
  "users.$get": { cache: true, cacheTime: 30000 },
  "/admin/*": { auth: true, retry: 0 },
});

Your API schema generates a fully typed SDK, but the generated code only knows about endpoints and types. Real projects still need caching policies, retry rules, auth settings, and response mappers. $configure lets you inject all of that into the SDK in one place, so every request comes pre-configured the moment you access it. It also makes testing easier by letting you swap in mocks without tools like msw or nock.

Version 8.0 is a foundational release — we replaced the entire HTTP layer with native fetch, added first-class streaming, modernized every React hook with useSyncExternalStore, and introduced client/server cache modes for safe server-side usage. Every change is driven by a single goal: fewer abstractions, more platform alignment, better DX.

Welcome to the official migration guide for upgrading to HyperFetch v7. This guide will walk you through the key changes, breaking updates, and recommended steps to update your codebase efficiently.

Version 7.0 is not just an update - it's a complete reimagining of the developer experience. We've listened to your feedback and created tools that will fundamentally change how you build and debug data-driven applications. We've modernized the entire library to provide a more robust and flexible data-fetching solution.

The most important update to date has been released!​

New version of our library got released and with it, dozens of updates and new features, additional tests, remodeled and refined typescript that should satisfy the most demanding users.

We provided many, many updates and enhancements to improve the experience and ensure everything is working just great.

That’s not all, we are extremely excited to present you our first integrations - Firebase, Axios and GraphQL adapters!

Hyper Fetch 3.0 is out! 🎉🎉​

It has been exactly one year since the first version of Hyper Fetch was presented, and two years since work on the tool began. The initial scope, which was ambitious in its assumptions, has been extended. We are proud to announce that today, Hyper Fetch supports HTTP, GraphQL, WebSockets, Server-Sent Events, React Hooks, persistence, and offline-first functionality, among many other features.

Let's take a look on the 3.0 highlights and sum up 2022 together with plans for an even better 2023!

Welcome! 👋​

We are very happy to introduce Hyper Fetch tool that helps to interact with requests on the frontend side. We start from alpha stage as we believe that our ideas with the community involvement may resolve with the best fetching tool out there.

The idea for Hyper Fetch was shaped over the years of work on many projects in which I encountered various problems in the subject of fetching, request queueing, persistence, offline and data caching. This project was created to solve most of them, and the most problematic or seemingly inaccessible - due to the level of complexity.