node-fetch
A light-weight module that brings the Fetch API to Node.js
Runssource: GitHubJavaScriptMITcommit 8b3320d2a7c0
JavaScript, MIT licensed. The project labels itself: fetch, fetch api, hacktoberfest, http, http client, node fetch, promise and spec compliant.
node-fetch runs. An Argusic agent installed it in 0.3 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
node-fetch v3.1.1 installed, builds cleanly, all 389 functional tests pass with 4 pending (1 IPv6 skip patched), module loads and works via ESM import against a local HTTP server.
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. 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.
- IPv6 test fails - EADDRNOTAVAIL address not available ::15 minutes
- Install time
- under a minute
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm test: 389 passing, 4 pending, 0 failing. Manual ESM import test: fetch against local HTTP server returned 200.
- Model tokens used
- 84,546
- Exact commit tested
- 8b3320d2a7c0
- 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.
tokens used
84,546
All 389 tests passing, 4 pending (3 pre-existing + 1 my IPv6 skip). Let me record the final state a…
Here's the summary:
**Install**: `npm install` succeeded with 850 packages, only deprecation warnings (no errors).
**Error found**: The IPv6 test (`describe('node-fetch using IPv6')`) failed with `EADDRNOTAVAIL` be…
**Fix**: Added a `before` hook in `test/main.js` that probes for IPv6 (`server.listen(0, '::1')`) a…
**Verification**:
- `npm test`: 389 passing, 4 pending, 0 failing
- Node ESM import verification: `fetch('http://127.0.0.1:{port}/test')` returned status 200 with bo…
- The `test-types` failures are all in `@types/node` (upstream dependency), not in node-fetch's own…
- 1 pre-existing lint warning in `@types/index.test-d.ts` (upstream `no-new`), unrelatedReplay 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 0.3 minutes.
- Recovered from all 1 error 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 0.3 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)
fetchfetch-apihacktoberfesthttphttp-clientnode-fetchpromisespec-compliantstreamwhatwgwhatwg-fetch
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/node-fetch)Questions
- Does node-fetch run?
- Yes. node-fetch runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test node-fetch?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8b3320d2a7c0. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test node-fetch?
- 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 node-fetch take to install?
- 0.3 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 node-fetch need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing node-fetch?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for node-fetch?
- 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.