zustand
🐻 Bear necessities for state management in React
Runssource: GitHubTypeScriptMITcommit d7a5583cffd8
TypeScript, MIT licensed. The project labels itself: hacktoberfest, hooks, react, react context, reactjs, redux and state management.
zustand runs. An Argusic agent installed it in 23 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Zustand v5.0.15 installs, builds, passes its full test suite (224/224), type-checks, and lints cleanly on Node 22
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.
- jsdom@30 requires Node >=22, container has Node 18.19.1; also @exodus/bytes is ESM-only but html-encoding-sniffer/whatwg-url/jsdom all require() it20 minutes
- Install time
- 23 minutes
- Cold machine to finish
- 24 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- pnpm test exited 0: 224/224 tests passed across 13 files, build completed, tsc --noEmit passed, eslint . passed
- Model tokens used
- 205,354
- Exact commit tested
- d7a5583cffd8
- 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.
All three verification commands pass: tests (224/224 pass), types check (no errors), lint (no issue… Let me now compose the final result. The project is [Zustand](https://github.com/pmndrs/zustand) v5.0.15 — a React state management libr… **Errors encountered & fixes** 1. **`ERR_REQUIRE_ESM` / jsdom@30 Node version mismatch** — [email protected] requires Node >=22 (its `h… 2. **`@exodus/bytes` ESM-only with CJS consumers** — Even on Node 22, the `exports` map redirect wa… **What was verified** - `pnpm test` → all 224 tests pass (13 files) - `pnpm run build` → builds all entry points (CJS + ESM + types) - `pnpm run test:types` → `tsc --noEmit` passes - `pnpm run test:lint` → `eslint .` passes - `pnpm run test:format` → `prettier . --list-different` (nothing outstanding)
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.
- 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
- Took 23 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 5 hacktoberfest projects Argusic has installed and timed, zustand was the 5th fastest to reach a running state, and 4 of 5 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
Topics (from GitHub)
hacktoberfesthooksreactreact-contextreactjsreduxstate-management
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/zustand)Questions
- Does zustand run?
- Yes. zustand runs. Argusic installed and launched it on a clean machine in 23 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test zustand?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d7a5583cffd8. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test zustand?
- The run that produced this verdict cost $0.21: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does zustand take to install?
- 23 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 zustand need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing zustand?
- 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.
- How does zustand compare with the alternatives?
- Of the 5 hacktoberfest projects Argusic has installed and timed, zustand was the 5th fastest to reach a running state, and 4 of 5 reached one at all.
- Where is the evidence for zustand?
- 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.