shaders
WebGPU components for React, Vue, Svelte, Solid, JS & Framer
Runssource: GitHubTypeScriptMITcommit 81fd4ece5d49
TypeScript, MIT licensed. The project labels itself: cli, javascript, mcp, react, shaders, solid, svelte and vue.
shaders runs. An Argusic agent installed it in 9 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
A fresh pnpm install and full monorepo build succeed with no warnings, all 1815 tests pass, the shaders CLI answers --version (4.0.4) and --help, and the build outputs 200 registered shaders plus loadable js/react/vue/svelte/partner packages, with WebGPU rendering not exercisable because the container has no GPU.
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.
- WebGPU rendering cannot run in this container (no GPU/WebGPU device); renderer degrades gracefully by design and GPU-free tests pass3 minutes
- Preinstalled Node 18 without pnpm; repo requires Node 22.20.x and pnpm 10.0.02 minutes
- pnpm warned 'build scripts ignored' for esbuild, sharp, svelte-preprocess, vue-demi because package.json pnpm.onlyBuiltDependencies was []2 minutes
- Install time
- 9 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pnpm test exited 0 (269 files, 1815 tests passed); pnpm lib:build '8 successful, 8 total'; node packages/shaders/dist/cli.js --version printed 4.0.4; shaders-core/registry getAllShaders() returned 200; built js/react/vue/svelte/partner packages imported successfully; sharp encoded a real 4x4 PNG (95 bytes)
- Model tokens used
- 382,638
- Exact commit tested
- 81fd4ece5d49
- 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.
- Real behavior verified: CLI (`shaders --version` → `4.0.4`, `--help` exit 0), core registry (200 …
- No third-party keys required — no real credentials needed.
- Not verifiable here: actual WebGPU frames (no GPU in container; renderer degrades gracefully by d…
tokens used
382,638
Everything is verified on the final state. Let me record the timing accurately: the label time comp…
**Summary of what happened:**
- `Node 18` was preinstalled; repo requires Node 22.20.x + pnpm 10. Installed Node 22.20.0 locally …
- One real repo defect found and fixed: `package.json` had `"pnpm": {"onlyBuiltDependencies": []}` …
- Real behavior verified: CLI (`shaders --version` → `4.0.4`, `--help` exit 0), core registry (200 …
- No third-party keys required — no real credentials needed.
- Not verifiable here: actual WebGPU frames (no GPU in container; renderer degrades gracefully by d…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 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
- Took 9 minutes to install, slower than the median of the 80 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 81 cli projects Argusic has installed and timed, shaders was the 61st fastest to reach a running state, and 74 of 81 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.
- A quick evaluation: it was running 9 minutes after the clone.
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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/shaders)Questions
- Does shaders run?
- Yes. shaders runs. Argusic installed and launched it on a clean machine in 9 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test shaders?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 81fd4ece5d49. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test shaders?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does shaders take to install?
- 9 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 shaders need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing shaders?
- 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 shaders compare with the alternatives?
- Of the 81 cli projects Argusic has installed and timed, shaders was the 61st fastest to reach a running state, and 74 of 81 reached one at all.
- Where is the evidence for shaders?
- 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.