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 0.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.
With checksum-verified Node v24.22.2 and npm ci, npm test exited 0 (7 Node, 1,439 AVA, and 32 Vitest tests passed), the CLI built a fresh site, and its dev server returned HTTP 200 on / and /about/.
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.
- The initial npm test browser phase failed because Playwright Chromium was not installed, so Vitest executed no browser tests.1 minute
- Node 18.19.1 did not satisfy the package's >=22.15 engine requirement; npm install exited 127 in prepare because simple-git-hooks was unavailable.0.5 minutes
- Direct import of @11ty/eleventy/package.json failed with ERR_PACKAGE_PATH_NOT_EXPORTED.
- A verification wrapper used Bash-only PIPESTATUS syntax under /bin/sh and exited with Bad substitution before creating the consumer page.
- Install time
- under a minute
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- npm ci exited 0; npm test exited 0 with Node 7/7, AVA 1439 passed and 28 skipped, and Vitest 4 files/32 passed; node cmd.cjs --version printed 4.0.0-alpha.10; curl http://127.0.0.1:8099/ and /about/ returned 200; the packed tarball installed in a separate project and its eleventy build exited 0.
- Model tokens used
- 133,805
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 73ms: --- build --- [11ty] Writing ./_site/index.html from ./index.md (liquid) [11ty] Wrote 1 file in 0.07 seconds (v4.0.0-alpha.10 no config file) CONSUMER_BUILD_EXIT=0 --- generated HTML --- <h1>Packaged Install</h1> <p>Built by the locally packed Eleventy tarball.</p> -- generated size -- 79 _site/index.html tokens used 133,805
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 0.5 minutes, faster than the median of the 4 comparable projects Argusic has measured.
- 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.
Of the 5 blog-engine projects Argusic has installed and timed, buildawesome was the 2nd 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.
- A quick evaluation: it was running 0.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 1 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. 2 attempts are 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.05: 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?
- 0.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.
- How does buildawesome compare with the alternatives?
- Of the 5 blog-engine projects Argusic has installed and timed, buildawesome was the 2nd fastest to reach a running state, and 5 of 5 reached one at all.
- Where is the evidence for buildawesome?
- 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.