buildawesome
A simpler site generator. Transforms a directory of templates (of varying types) into HTML.
Runssource: GitHubhomepageJavaScriptMITcommit cdc06972c45d
JavaScript, MIT licensed. The project labels itself: blog engine, documentation tool, eleventy, javascript, static site generator and templates.
buildawesome runs. An Argusic agent installed it in 1.5 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Eleventy 4.0.0-alpha.10 installed on Node 22.15.0, all 1439 ava tests and 7 node tests pass, CLI builds sites correctly
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.
- spawnAsync rejected on stderr warnings from experimental-strip-types2 minutes
- Node.js 18.19.1 below required >=22.151.5 minutes
- 18 test failures from TypeScript extension expectations1 minute
- npm install failed on simple-git-hooks script0.5 minutes
- Install time
- 2 minutes
- Cold machine to finish
- 20 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- npm test server ran with NODE_OPTIONS=--experimental-strip-types: ava 1439 passed 0 failed, node --test 7 passed 0 failed, and node cmd.cjs --version returned 4.0.0-alpha.10 with real build working
- Model tokens used
- 344,040
- Exact commit tested
- cdc06972c45d
- 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.
| Error | Fix | |-------|-----| | Node.js 18.19.1 (requires >=22.15) | Installed Node 22.15.0 via `nvm` | | `npm install` failed: `simple-git-hooks: not found` | Ran `npm install --ignore-scripts`, then `n… | Ava test `spawnAsync` rejects on stderr warnings when `--experimental-strip-types` emits Experime… | 18 ava test failures due to hardcoded `.mts`/`.cts`/`.ts` extensions in test expectations | Re-ra… **Final verification:** - `node cmd.cjs --version` → `4.0.0-alpha.10` - Ava suite: **1439 passed, 28 skipped, 0 failed** - Node test runner: **7 passed, 0 failed** - Real Eleventy build from scratch (`node cmd.cjs --formats=md` on a markdown file): wrote `_site/i… - External keys: none required (no external API dependencies)
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 1.5 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 1.5 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)
blog-enginedocumentation-tooleleventyjavascriptstatic-site-generatortemplates
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/buildawesome)Questions
- Does buildawesome run?
- Yes. buildawesome runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test buildawesome?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit cdc06972c45d. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test buildawesome?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does buildawesome take to install?
- 1.5 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 buildawesome need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing buildawesome?
- 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 buildawesome?
- 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.