redux
A JS library for predictable global state management
Runssource: GitHubTypeScriptMITcommit 56abca474992
TypeScript, MIT licensed. The project labels itself: redux.
redux runs. An Argusic agent installed it in 1 minute and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Redux installs with pnpm on Node 18 but requires Node >=22.12 to run its native-dependent toolchain (vitest with typecheck, oxfmt format checking, oxlint linting, tsdown build). Under Node 22, all 119 tests pass, the build produces 5 bundle formats, and format/lint checks are clean.
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 v18.19.1 system Node is too old for native optional dependencies (oxfmt, oxlint, rolldown all require >=20.19 or >=22.12); native binaries not downloaded by pnpm install4 minutes
- Install time
- 1 minutes
- Cold machine to finish
- 20 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- vitest --run --typecheck with Node 22: 18 test files, 119 tests passed, no type errors. tsdown build with Node 22: 5 output bundles (modern ESM, legacy ESM, browser ESM, CJS, type definitions). oxfmt --check with Node 22: 117 files correct. oxlint with Node 22: no errors. TEST_DIST=true vitest against built dist: 9 files, 82 tests passed.
- Model tokens used
- 176,248
- Exact commit tested
- 56abca474992
- 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.
Type Errors no errors Start at 07:36:01 Duration 2.29s (transform 295ms, setup 0ms, collect 545ms, tests 58ms, environment 1ms, prepare… === FORMAT CHECK === Checking formatting... All matched files use the correct format. Finished in 2985ms on 117 files using 4 threads. === LINT === All results are in and the repository works end-to-end. Here's the final report: tokens used 176,248 All results are in and the repository works end-to-end. Here's the final report:
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 1 minute.
- 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 1 minutes after the clone.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/redux)Questions
- Does redux run?
- Yes. redux runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test redux?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 56abca474992. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test redux?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does redux take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does redux need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing redux?
- 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 redux?
- 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.