better-fetch
A fetch wrapper that returns data and error objects with type inference and auth features
Library Rated 7 Oct 2026
- Built by
Beka
Bloat
265/500Where it landed on the scale
0
300
400
Summary
better-fetch is a real, working, documented open-source library that has been maintained for about 29 months and is the HTTP layer for the author's better-auth ecosystem. It solves a genuine developer problem, but it is a free MIT library with no payments or pricing, so its viability and moat rest on adoption and its tie to a larger project rather than on any business of its own.
Bloat · Not much here works or looks likely to last, yet.
Breakdown
Five measures, 100 points each. Open the receipts under any of them to see the posts and pages behind the points.
Viability
Is there a real problem, someone who would pay, and a market this builder can actually reach?
A real developer problem with active, ongoing use, but there is no revenue model and no one pays; value is indirect, as a dependency of the better-auth ecosystem.
42/100
Rubric 41–60Plausible users and a believable way to charge them. Not yet shown to work.
Receipts (4)
States a concrete problem: wanting data and error objects instead of a raw Response, which came out of real work on better-auth.
“I made a fetch wrapper that returns data and error object instead of Response. While I was working on better auth, I start using ofetch which is also a wrapper over fetch. I like many of its features, but I wanted to have the response as data and error. And this isn't the first time I wanted this, so I created a fetch wrapper that add this, along with some features borrowed from ofetch. https:/”
Post · @bekacru_c · 22 Apr 2024 · open on Telegram (opens in a new tab)
Reports 31k weekly downloads, which suggests real use (a usage signal, not an audience count).
“better-fetch has 31k downloads per week 🤯”
Post · @bekacru_c · 11 Feb 2025 · open on Telegram (opens in a new tab)
The site shows no pricing, payments or account system; it is a free MIT library.
Checked 7 Oct 2026 · better-fetch.vercel.app (opens in a new tab)
The author uses it in the better-auth client, which gives it a real anchor use.
“On better-fetch: I've shifted the namespace to @better-fetch/fetch from @better-tools/fetch. The old one is deprecated. Hopefully, no one was doing anything serious with the library. I'm using better-fetch for better-auth client, so I'll make sure to maintain it properly from now on and follow semantic versioning. https://github.com/Bekacru/better-fetch”
Post · @bekacru_c · 9 May 2024 · open on Telegram (opens in a new tab)
Moat
What stops someone copying it?
Fetch wrappers are easy to rebuild, so the edge is execution, typed schemas and plugins, and being bundled into better-auth. There is no proprietary data or hard technology, though the better-auth tie gives it some pull.
30/100
Rubric 21–40The only edge is execution, or being first.
Receipts (4)
The core is a wrapper over fetch, modelled on features from ofetch, which many developers could rebuild.
“I made a fetch wrapper that returns data and error object instead of Response. While I was working on better auth, I start using ofetch which is also a wrapper over fetch. I like many of its features, but I wanted to have the response as data and error. And this isn't the first time I wanted this, so I created a fetch wrapper that add this, along with some features borrowed from ofetch. https:/”
Post · @bekacru_c · 22 Apr 2024 · open on Telegram (opens in a new tab)
Plugins that carry schemas, retry options and inferred dynamic params add depth beyond a thin wrapper.
“Better Fetch v1.1 is realeased 🎉 - Advanced Retry Options (https://better-fetch.vercel.app/docs/timeout-and-retry#advanced-retry-options) - Plugins now can define schema (https://better-fetch.vercel.app/docs/plugins#schema) - you can document your whole api and ship it as a plugin :)) - Plugins can define more options to be passed to a fetch call (https://better-fetch.vercel.app/docs/plugins#g”
Post · @bekacru_c · 23 Jul 2024 · open on Telegram (opens in a new tab)
Used by the better-auth client, which gives it some built-in distribution.
“On better-fetch: I've shifted the namespace to @better-fetch/fetch from @better-tools/fetch. The old one is deprecated. Hopefully, no one was doing anything serious with the library. I'm using better-fetch for better-auth client, so I'll make sure to maintain it properly from now on and follow semantic versioning. https://github.com/Bekacru/better-fetch”
Post · @bekacru_c · 9 May 2024 · open on Telegram (opens in a new tab)
MIT-licensed with 30 releases, so competitors can freely fork it.
Checked 7 Oct 2026 · github.com/Bekacru/better-fetch (opens in a new tab)
Momentum
Did the updates keep coming?
Shipped across 29 months, with 30 releases and updates in 18 of 30 months. The pace was bursty, with gaps in 2025, but the project has stayed alive through September 2026.
84/100
- Sustained shipping60/60
Worked on across 29 months.
- Consistency24/40
Updates in 18 of 30 months.
Receipts (2)
Earliest post about it.
“I made a fetch wrapper that returns data and error object instead of Response. While I was working on better auth, I start using ofetch which is also a wrapper over fetch. I like many of its features, but I wanted to have the response as data and error. And this isn't the first time I wanted this, so I created a fetch wrapper that add this, along with some features borrowed from ofetch. https:/”
Post · @bekacru_c · 22 Apr 2024 · open on Telegram (opens in a new tab)
Most recent post about it.
“> Besides better-auth, are there any other projects you’re currently working on or thinking about? there are other projects like better-call and better-fetch but they are still related to better auth so not really”
Post · @bekacru_c · 19 Feb 2025 · open on Telegram (opens in a new tab)
Infrastructure
Does a real, working product exist?
A full working library exists, with typed schemas, plugins, retry and auth features, a docs site and 30 releases. It is a library rather than a hosted service, so there is no backend or status page.
84/100
- It's live20/20
https://github.com/Bekacru/better-fetch responded when checked.
- HTTPS5/5
Hosted on a platform (store, GitHub or Telegram) — HTTPS is the platform's.
- Real product35/35
A full working published library with docs, typed schemas, plugins, retry and auth handling, and 30 tagged releases.
- Own home0/10
Only on a free subdomain or link-in-bio page.
- Maintained15/15
Last sign of shipping 2026-09-11.
- Operations9/15
A dedicated docs site with type hover and a release history on GitHub and npm. There is no API service, status page or accounts, which are not relevant to a library anyway.
Receipts (5)
https://github.com/Bekacru/better-fetch responded when checked.
Checked 7 Oct 2026 · github.com/Bekacru/better-fetch (opens in a new tab)
30 releases, an MIT license, a live repo and a recent push on 2026-09-11.
Checked 7 Oct 2026 · github.com/Bekacru/better-fetch (opens in a new tab)
v1.1 shipped retry options, plugin schemas and inferred parameters.
“Better Fetch v1.1 is realeased 🎉 - Advanced Retry Options (https://better-fetch.vercel.app/docs/timeout-and-retry#advanced-retry-options) - Plugins now can define schema (https://better-fetch.vercel.app/docs/plugins#schema) - you can document your whole api and ship it as a plugin :)) - Plugins can define more options to be passed to a fetch call (https://better-fetch.vercel.app/docs/plugins#g”
Post · @bekacru_c · 23 Jul 2024 · open on Telegram (opens in a new tab)
Added Standard Schema compatibility, so validators other than zod work.
“released new version of better-fetch. it's now standard schema compatible. meaning you can use other validators instead of zod if they are compliant like valibot https://github.com/Bekacru/better-fetch”
Post · @bekacru_c · 11 Feb 2025 · open on Telegram (opens in a new tab)
A documentation site launched alongside v1.0.
“Heyy good people I’m excited about this one. Better Fetch version 1.0 is now out 🚀, and we have an amazing new documentation site to go with it 🥳 There are quite a few API changes and some new additions, but moving forward, the API will remain mostly consistent. Creating a good doc site was an important exercise for me, and I’m proud of the results. Check it out and let me know what you thin”
Post · @bekacru_c · 15 Jul 2024 · open on Telegram (opens in a new tab)
Sustainability
Is it being set up to last?
It is MIT-licensed with no payments, pricing or support channel, so it earns no money itself. It lasts because it is part of the better-auth ecosystem and the maintainer committed to maintaining it, but nothing on the project's own pages shows a funding model.
25/100
- Distribution12/30
A site on a free subdomain.
- Payments0/15
No payment provider found.
- Pricing0/10
No pricing found on the site.
- Revenue0/5
No posts mention customers, sponsorship or revenue, and no payment provider was found.
- Privacy policy0/7
No privacy policy found.
- Terms0/5
No terms of service found.
- Support0/8
No support contact found.
- Commitment13/20
Maintained steadily for over two years, with a semver pledge and a roadmap that was delivered, and it sits inside the better-auth organization. There is no evidence of dedicated funding or a dedicated community channel.
Receipts (5)
A site on a free subdomain.
Checked 7 Oct 2026 · better-fetch.vercel.app (opens in a new tab)
No payments, pricing or accounts were found on the site.
Checked 7 Oct 2026 · better-fetch.vercel.app (opens in a new tab)
Pledged to maintain it properly and follow semantic versioning.
“On better-fetch: I've shifted the namespace to @better-fetch/fetch from @better-tools/fetch. The old one is deprecated. Hopefully, no one was doing anything serious with the library. I'm using better-fetch for better-auth client, so I'll make sure to maintain it properly from now on and follow semantic versioning. https://github.com/Bekacru/better-fetch”
Post · @bekacru_c · 9 May 2024 · open on Telegram (opens in a new tab)
Announced typed routes and plugins ahead of time, and later releases delivered them (P17).
“https://github.com/Bekacru/better-fetch/tree/next Better fetch upcoming release will include typed routes, React hooks, and fetch plugins. I'll also be using typed routes for better auth. I'm not going to create a client library for better-auth. It's mostly about making API calls. So we'll just export typed routes for better fetch and you just call those apis and you get typesaftey. For csrf pr”
Post · @bekacru_c · 3 May 2024 · open on Telegram (opens in a new tab)
Commits and releases continued through 2026, and the repo now lives under the better-auth org.
Checked 7 Oct 2026 · github.com/Bekacru/better-fetch (opens in a new tab)