react-router
Declarative routing for React
Runssource: GitHubTypeScriptMITcommit 246ddbeced9c
TypeScript, MIT licensed.
react-router runs. An Argusic agent installed it in 44 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 138 unit test suites pass (2865 tests, 15 skipped), all 10 packages build cleanly, and individual integration tests against both vite-7-template and rsc-vite-framework templates pass under Playwright/Chromium.
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.
- Node.js 18.19.1 is below the required >=22.22.03 minutes
- Flaky timeout in special-characters-test.tsx when run in full suite (2 tests failed once)
- Install time
- 44 minutes
- Cold machine to finish
- 85 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- pnpm test exited 0, 138 suites passed, 2865 tests passed, 2880 total, 15 skipped; integration tests abort-signal (passed 1), blocking (passed 1), bug-report (passed 1), and RSC template tests (passed individually) work but batch runs hang due to 128 parallel workers from 256 CPUs
- Model tokens used
- 340,215
- Exact commit tested
- 246ddbeced9c
- 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.
1791276119
exec
/bin/sh -lc 'end=$(date +%s); start=$(echo "1791273479"); echo "Elapsed: $(( (end - start) / 60 )) …
succeeded in 0ms:
Elapsed: 44 minutes
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 4…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 44, "errors": [{"msg": "No…
2026-10-06T08:42:12.022318Z ERROR codex_core::session: failed to record rollout items: thread 01a11…
tokens used
340,215Replay 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 2 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
- Took 44 minutes to install, slower than the median of the 30 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 31 TypeScript projects Argusic has installed and timed, react-router was the 31st fastest to reach a running state, and 22 of 31 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.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/react-router)Questions
- Does react-router run?
- Yes. react-router runs. Argusic installed and launched it on a clean machine in 44 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test react-router?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 246ddbeced9c. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test react-router?
- The run that produced this verdict cost $0.26: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does react-router take to install?
- 44 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-router need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing react-router?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does react-router compare with the alternatives?
- Of the 31 TypeScript projects Argusic has installed and timed, react-router was the 31st fastest to reach a running state, and 22 of 31 reached one at all.
- Where is the evidence for react-router?
- 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.