react-konva
React components for the Konva 2d canvas library. Build interactive graphics, design editors, and whiteboards with JSX.
Runssource: GitHubhomepageTypeScriptMITcommit 92117241d76b
TypeScript, MIT licensed. The project labels itself: canvas, canvas editor, design editor, draw graphics, konva, konva framework, react and react canvas.
react-konva runs. An Argusic agent installed it in 13 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 196 browser tests pass against Chromium, TypeScript checks pass, the build produces es/ and lib/ output, SSR rendering succeeds across CommonJS and ES module entry points, package exports resolve correctly in ESM/CJS/Node10/Bundler modes, and DevTools registration and canvas commits are functional.
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.
- npm install failed on Node 18: Cannot read properties of null (reading 'edgesOut') - peer dependency conflict with vitest@4 requiring Node >=205 minutes
- Playwright and vitest@4 require Node >=20 but only Node 18 was available3 minutes
- Install time
- 13 minutes
- Cold machine to finish
- 30 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- npx vitest run exited 0 with 25 files/196 tests passed; npm run test:typings passed; node build.mjs built es/ and lib/; node test/11-ssr.mjs, test/24-package-exports.mjs, test/29-devtools.mjs all passed
- Model tokens used
- 177,402
- Exact commit tested
- 92117241d76b
- 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.
1. **npm install failed** on Node 18 with `Cannot read properties of null (reading 'edgesOut')` — p… 2. **Playwright / vitest require Node >=20** — Node 18 in the container couldn't run them. Fixed by… **Verification results with Node 22:** | Suite | Result | |---|---| | `vitest run` (dev) | 25 files, 196 tests passed | | `NODE_ENV=production vitest run` | 25 files, 196 tests passed | | `npm run test:typings` | passed | | `node build.mjs` | built `es/` and `lib/` | | SSR test (`11-ssr.mjs`) | all entry points OK | | Package exports (`24-package-exports.mjs`) | all OK | | DevTools (`29-devtools.mjs`) | all OK |
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 13 minutes.
- 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.
- 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.02 |
Topics (from GitHub)
canvascanvas-editordesign-editordraw-graphicskonvakonva-frameworkreactreact-canvasvisualizationwhiteboard
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/react-konva)Questions
- Does react-konva run?
- Yes. react-konva runs. Argusic installed and launched it on a clean machine in 13 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test react-konva?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 92117241d76b. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test react-konva?
- 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 react-konva take to install?
- 13 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-konva need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing react-konva?
- 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.
- Where is the evidence for react-konva?
- 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.