dumi
📖 Static Site Generator for component library development
Runssource: GitHubhomepageJavaScriptMITcommit 8c4150bf66ad
JavaScript, MIT licensed. The project labels itself: docs generator, library development, static site generator and umi.
dumi runs. An Argusic agent installed it in 14 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Dependencies installed, father TS build compiles 70 files to dist/, Rust WASM plugin crate built, all 139 tests pass, and an end-to-end build of the normal example produces a valid docs-dist with HTML output.
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 60 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.
- swc_plugin_react_demo.wasm missing (2 techStack tests fail)6 minutes
- cargo: not found (Rust toolchain missing)3 minutes
- pnpm: not found1 minute
- node bin/dumi.js --help prints 'Node 20 is required when using utoopack'
- Install time
- 14 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- npx vitest run returned 18 test files passed, 139 passed, 12 skipped; examples/normal/dist/ built (16 MB) with correct index.html
- Model tokens used
- 227,899
- Exact commit tested
- 8c4150bf66ad
- 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.
- `pnpm: not found` — installed pnpm 8.15.9 locally - `cargo: not found` — installed Rust toolchain via rustup (nightly-2026-02-05) - `swc_plugin_react_demo.wasm` missing — built the SWC WASM plugin crate with `cargo build --target… - Node 18 vs Node 20 utoopack requirement — this is a transitive dependency from `@umijs/preset-umi… tokens used 227,899 All 18 test files passed (139 passed, 12 skipped). The project builds and runs. Here's the final re… **Errors encountered and fixed:** - `pnpm: not found` — installed pnpm 8.15.9 locally - `cargo: not found` — installed Rust toolchain via rustup (nightly-2026-02-05) - `swc_plugin_react_demo.wasm` missing — built the SWC WASM plugin crate with `cargo build --target… - Node 18 vs Node 20 utoopack requirement — this is a transitive dependency from `@umijs/preset-umi…
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 14 minutes.
- Recovered from all 4 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.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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 | Runs | 100.00 | 0.08 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.11 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/dumi)Questions
- Does dumi run?
- Yes. dumi runs. Argusic installed and launched it on a clean machine in 14 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test dumi?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8c4150bf66ad. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test dumi?
- 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 dumi take to install?
- 14 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 dumi need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing dumi?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for dumi?
- 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.