react-reader
An ePub-reader for React, powered by Epub.js
Runs with mockssource: GitHubhomepageTypeScriptApache-2.0commit 70d489366b3b
TypeScript, Apache-2.0 licensed. The project labels itself: epub reader, react and reader.
react-reader runs, with stand-ins for the services it depends on. An Argusic agent installed it in 10.8 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm ci installs cleanly; npm test now passes 2 suites/4 tests; npm run build and build-vercel both exit 0; vite preview serves the built demo with HTTP 200 on /, /files/alice.epub, and the app JS bundle.
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 86 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.
- npm test exited 1: No tests found - the repo ships zero test files1 minute
- Test TS errors: verbatimModuleSyntax from root tsconfig leaked into test compile; @testing-library/user-event not installed; matcher types not loaded1 minute
- Test UX bugs in my new tests (undefined button, wrong EpubView assertion, mock typing)1 minute
- Demo smoke: vite preview served 404 after library build clobbered the demo dist1 minute
- unzip/headless browser not installed in container; xdg-open missing so vite dev/preview print a harmless open-error
- Install time
- 11 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- npm test exited 0 with 2 suites passed/4 tests passed (components/ReactReader, components/EpubView); npm run build exited 0 producing dist/react-reader.es.js and dist/react-reader.umd.js; npm run build-vercel exited 0; vite preview on port 4181 answered 200 on /, 200 on /files/alice.epub (189793 bytes, zip OK, sha256 matches public/files/alice.epub), 200 on the app JS bundle; no browser available so tier2_mock is reported
- Model tokens used
- 650,664
- Exact commit tested
- 70d489366b3b
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- Verified: `npm test` → `Test Suites: 2 passed, 2 total / Tests: 4 passed, 4 total`, exit 0. `npm … - Why `tier2_mock`: real epub rendering requires a browser and none is installed in this container;… AR tokens used 650,664 Done. Summary: - Installed with `npm ci` (exit 0; npm audit reports 64 advisories in transitive deps, pre-existing… - Root cause found: the repo has zero test files, so `npm test` exited 1 with "No tests found". - Fix: added 4 real tracked tests under `components/` (ReactReader: full UI render, TOC toggle + `l… - Verified: `npm test` → `Test Suites: 2 passed, 2 total / Tests: 4 passed, 4 total`, exit 0. `npm … - Why `tier2_mock`: real epub rendering requires a browser and none is installed in this container;… AR
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
- Installed in 10.8 minutes.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- 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
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Unverified | 80.00 | 0.01 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.14 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/react-reader)Questions
- Does react-reader run?
- react-reader runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 11 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test react-reader?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 70d489366b3b. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test react-reader?
- The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does react-reader take to install?
- 10.8 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 react-reader need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing react-reader?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for react-reader?
- 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.