About five years ago, I began developing what I hoped would be the data fetcher of the future - HyperFetch. It was a long and challenging journey, but I believe it has turned out to be successful and I hope it will be useful to the community.

So what is HyperFetch?

In short, it’s a data-fetching library. If you take Axios and TanStack Query and combine them into one, you get HF. The name doesn’t imply faster network requests. My goal was to speed up development, improve usability, and eliminate repetitive, tedious boilerplate. It should be quick to write and easy to maintain, while also scaling well.

I’ve spent most of my career building UI kits, reusable architectures, and components to empower developers at the organizations I’ve worked with. After thousands of hours and many years, I feel I’ve poured all that experience into this library.

Along this path I was inspired by many - trpc, tanstack query, swr, rtk, axios, shadcn - but I think my approach is a little different. I integrated the hooks directly with the fetching logic to give them a deeper understanding of the data flow and structure.

There are good reasons to remain agnostic and provide very open-ended hooks, like in tanstack query or swr. But there are also many reasons why a more tightly coupled system like HyperFetch can be powerful. We know the expected data structure, can track upload/download progress, and even support real-time communication which I do with dedicated "sockets" package.

You’ll find more reasons and examples of how HF can improve your workflows in the comments. I’ll leave you with our brand-new docs to explore!

https://hyperfetch.bettertyped.com/