hyper-fetch

⚡ Fetching and realtime data exchange framework.

Runssource: GitHubTypeScriptApache-2.0commit f2baf196d792

TypeScript, Apache-2.0 licensed. The project labels itself: api client, axios, cache, data fetching, fetch, firebase, graphql and http client.

hyper-fetch runs. An Argusic agent installed it in 26 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All 11 test suites pass (8653 tests in 394 files) on Node 22 with pnpm. The monorepo installs, builds, typechecks, lints, and runs all tests for all non-Firebase packages.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 97.5 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
97.5 / 100
cost of the verifying run
$0.10 (measured)
recorded runs
2
last tested
stars
1,333
forks
0
open issues
0
watchers
0
created
-
last push
-

Subject data from GitHub, linked at the top of this page. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing hyper-fetch, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Node v18 lacks styleText (Vite 8 requirement)5 minutes
  • GraphQL adapter tests fail: CloseEvent not defined in Node 223 minutes
  • pnpm not found in PATH2 minutes
  • install-peers.js crashes on ESM-only chalk v52 minutes
Install time
26 minutes
Cold machine to finish
25 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
pnpm exec nx test <pkg> on core/sockets/react/axios/graphql/trpc/orpc/hono/elysia/plugin-devtools/cli, 394 test files, 8653 tests all passed
Model tokens used
74,644
Exact commit tested
f2baf196d792
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- **Core**: 111 files, 2780 tests passed
- **Sockets**: 66 files, 1211 tests passed
- **React**: 125 files, 2026 tests passed
- **GraphQL**: 19 files, 396 tests passed
- **Axios**: 2 files, 37 tests passed
- **tRPC**: 19 files, 1330 tests passed
- **oRPC**: 22 files, 502 tests passed
- **Hono**: 13 files, 164 tests passed
- **Elysia**: 5 files, 109 tests passed
- **DevTools**: 5 files, 54 tests passed
- **CLI**: 7 files, 44 tests passed
Firebase/firebase-admin excluded (need emulators). Elysia bun tests excluded (Bun not installed). A…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 26 minutes to install, slower than the median of the 39 comparable projects Argusic has measured.

Of the 40 api-client projects Argusic has installed and timed, hyper-fetch was the 39th fastest to reach a running state, and 25 of 40 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs95.000.18
Argusic Runner1/3Runs100.000.10

Topics (from GitHub)

api-clientaxioscachedata-fetchingfetchfirebasegraphqlhttp-clientnextjsofflineopenapireactreact-hooksreact-queryrealtimesseswrtrpctypescriptwebsockets

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/hyper-fetch.svg)](https://argusic.com/subject/hyper-fetch)

Questions

Does hyper-fetch run?
Yes. hyper-fetch runs. Argusic installed and launched it on a clean machine in 26 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test hyper-fetch?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit f2baf196d792. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test hyper-fetch?
The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does hyper-fetch take to install?
26 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does hyper-fetch need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing hyper-fetch?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does hyper-fetch compare with the alternatives?
Of the 40 api-client projects Argusic has installed and timed, hyper-fetch was the 39th fastest to reach a running state, and 25 of 40 reached one at all.
Where is the evidence for hyper-fetch?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion