ffetch
TypeScript-first fetch wrapper with configurable timeouts, retries, and circuit-breaker baked in.
Runssource: GitHubTypeScriptMITcommit f20c1c383e67
TypeScript, MIT licensed. The project labels itself: backoff, fetch, http client, javascript, production ready, resilience and typescript.
ffetch runs. An Argusic agent installed it in 2 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
With Node 22.23.4, npm ci installs cleanly, tsup builds dist, vitest passes 27 files/274 tests with 99.31% coverage, and the built library serves real HTTP requests with working retries, status handling, and HttpError.
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 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . 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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Fresh npm install with npm 10 crashed: Cannot read properties of null (reading 'edgesOut')2 minutes
- Node 18 lacks node:util.styleText (v20.12+ API) required by vitest/rolldown; npm test crashed at startup1 minute
- Rolldown native binding missing after initial install (Cannot find native binding, asked for wasm fallback)1 minute
- Smoke script imported nonexistent dist/plugins/retry.js (retry is built-in, not a plugin)1 minute
- Install time
- 2 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- PATH=/tmp/node22/bin:$PATH npm test -> 27 files, 274 tests passed, exit 0; npm run test:ci -> 274 passed, 99.31% statement coverage; node smoke against a real local HTTP server using built dist -> /ok 200 JSON, 503 retried to 200 with 2 hits, /missing 404, throwOnHttpError raised HttpError
- Model tokens used
- 106,141
- Exact commit tested
- f20c1c383e67
- 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.
2. Fresh `npm install` with npm 10 crashed with `Cannot read properties of null (reading 'edgesOut'…
3. First test run on Node 22 failed with `Cannot find native binding` — the initial `node_modules` …
4. My first smoke script imported a nonexistent `dist/plugins/retry.js` (retry is built-in, not a p…
**Verified results**
- `npm install`/`npm ci`: 230 packages, no errors (only pre-existing engine warnings and 8 audit ad…
- `npm run build` (tsup): ESM + CJS + DTS build success.
- `npm test` (vitest) with Node 22.23.4: **27 test files, 274 tests passed**, exit 0.
- `npm run test:ci`: **274 passed**, coverage 99.31% statements / 98.12% branches, exit 0.
- `npm run lint`: exit 0. (Ran after `npm ci`; I checked the diff first and repaired the formatting…
- Real HTTP end-to-end (built `dist/index.js` against a local Node `http` server): `GET /ok` → `200…
- CJS entry verified: `require('dist/index.cjs')` and `require('dist/plugins/request-shortcuts.cjs'…
**Housekeeping:** `package-lock.json` was committed as v5.6.1 while `package.json` is v5.6.2 (drift…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.
- Installed in 2 minutes.
- 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 MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 2 minutes after the clone.
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
Topics (from GitHub)
backofffetchhttp-clientjavascriptproduction-readyresiliencetypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ffetch)Questions
- Does ffetch run?
- Yes. ffetch runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test ffetch?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f20c1c383e67. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test ffetch?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ffetch take to install?
- 2 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 ffetch need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ffetch?
- 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.
- Where is the evidence for ffetch?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.