vue-konva
Vue components for the Konva 2d canvas library. Build interactive graphics, design editors, and whiteboards in Vue.
Runssource: GitHubhomepageTypeScriptMITcommit eedf13ce9f42
TypeScript, MIT licensed. The project labels itself: canvas, canvas animation, canvas editor, design editor, graphics, konva, konvajs and shape.
vue-konva runs. An Argusic agent installed it in 13 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Standard npm install succeeded and, when run on Node 22, npm test exits 0 with 62 passing tests and npm run build exits 0 producing dist bundles (vue-konva.js, vue-konva.umd.js, vue-konva-core.js) plus .d.ts declarations; no tracked repo files were modified.
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, 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.
- Container has Node 18.19.1 but the project's devDependencies (vite 8.2.2, vitest 4.1.11, jsdom 30) require Node >=22 (vite: ^20.19||>=22.12, vitest: ^20||^22, jsdom: ^22.22.2). npm test crashed at startup: 'node:util' does not provide 'styleText'.8 minutes
- Rolldown's native binding was not installed (npm optional-dependencies bug, npm/cli#4828): 'Cannot find native binding ... @rolldown/binding-wasm32-wasi'.3 minutes
- Running tests on Node 20 failed with 'webidl.util.markAsUncloneable is not a function' because jsdom 30 pulls undici 8 which needs Node >=22.2 minutes
- Install time
- 13 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npm test (on Node 22) exited 0, 3 files passed, 62 passed, 1 skipped, no type errors; npm run build exited 0 (main+core bundles plus tsc declarations); scripts/check-dist.mjs exited 0: '23 declaration refs resolve; ESM entries and the UMD/CDN build work' and it mounted the UMD build in jsdom confirming a <v-circle> rendered a real Konva shape with a canvas element.
- Model tokens used
- 101,078
- Exact commit tested
- eedf13ce9f42
- 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.
## Findings **Install** - `npm install` succeeded (215 packages added, exit 0). No tracked repo files were modified. **Errors diagnosed and fixed** 1. **Node version gap (root cause):** Container has Node 18.19.1, but the project's pinned devDepen… 2. **Missing rolldown native binding:** `Cannot find native binding ... @rolldown/binding-wasm32-wa… 3. **jsdom/undici on Node 20:** `webidl.util.markAsUncloneable is not a function` — jsdom 30's undi… **Verification (real behavior, tier1_real)** - `npm test` on Node 22: exit 0 — **3 test files passed, 62 passed, 1 skipped, no type errors**. - `npm run build` on Node 22: exit 0 — built `vue-konva.js`, `vue-konva.umd.js`, `vue-konva-core.js… - `scripts/check-dist.mjs`: exited 0 with **"23 declaration refs resolve; ESM entries and the UMD/C… No third-party keys or network endpoints are involved in this library, so no mocks were needed.
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 3 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
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 5 canvas projects Argusic has installed and timed, vue-konva was the 3rd fastest to reach a running state, and 5 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.
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
Topics (from GitHub)
canvascanvas-animationcanvas-editordesign-editorgraphicskonvakonvajsshapevuevue-canvasvue-styleguidistwhiteboard
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/vue-konva)Questions
- Does vue-konva run?
- Yes. vue-konva runs. Argusic installed and launched it on a clean machine in 13 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test vue-konva?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit eedf13ce9f42. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test vue-konva?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does vue-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 vue-konva need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing vue-konva?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does vue-konva compare with the alternatives?
- Of the 5 canvas projects Argusic has installed and timed, vue-konva was the 3rd fastest to reach a running state, and 5 of 5 reached one at all.
- Where is the evidence for vue-konva?
- 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.