VvvebJs
Drag and drop page builder library written in vanilla javascript without dependencies or build tools.
Runssource: GitHubhomepageJavaScriptApache-2.0commit 1acbab7ebfe3
JavaScript, Apache-2.0 licensed. The project labels itself: bootstrap, bootstrap5, builder, drag and drop, editor, free, javascript and low code.
VvvebJs runs. An Argusic agent installed it in 7.3 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Express server on port 8080 serves editor.html with all JavaScript modules (builder, components-bootstrap5, components-widgets, undo, inputs), Bootstrap 5, CSS, demo pages (album, blog, carousel, landing et al.) and the save endpoint, all returning HTTP 200.
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.
- Submodule demo/landing directory was empty (not checked out)2 minutes
- node-sass compiled for Node NODE_MODULE_VERSION 108 but system has 109, breaking gulp SCSS compilation
- Install time
- 7 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- curl http://localhost:8080/editor.html returns 200; Vvveb.Builder.init found in page body; POST to /save.php with file+html writes content to disk verified by cat; all 14 critical asset paths return HTTP 200
- Model tokens used
- 99,858
- Exact commit tested
- 1acbab7ebfe3
- 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.
**Launch**: Started the Express server with `node save.js` on port 8080. The server prints "Started… **No test suite exists** — `npm test` just echoes "Error: no test specified" and exits 1. **Verification**: All 14 critical resources (editor.html, CSS, builder JS modules, bootstrap, demo … **Node-SASS mismatch** exists (compiled for Node 108, we have 109) which breaks `gulp` for SCSS com… tokens used 99,858 Here's the summary of everything I've done and found: **Install**: `npm install` succeeded (665 packages installed). The submodule `demo/landing` was not… **Launch**: Started the Express server with `node save.js` on port 8080. The server prints "Started… **No test suite exists** — `npm test` just echoes "Error: no test specified" and exits 1. **Verification**: All 14 critical resources (editor.html, CSS, builder JS modules, bootstrap, demo … **Node-SASS mismatch** exists (compiled for Node 108, we have 109) which breaks `gulp` for SCSS com…
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 7.3 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 Apache-2.0, 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.
- A quick evaluation: it was running 7.3 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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.04 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.02 |
Topics (from GitHub)
bootstrapbootstrap5builderdrag-and-dropeditorfreejavascriptlow-codeno-codenocodenodejsopen-sourcepage-builderscsssite-generatoruivanilla-javascriptwebsite-builderwebsite-generationwysiwyg
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/vvvebjs)Questions
- Does VvvebJs run?
- Yes. VvvebJs runs. Argusic installed and launched it on a clean machine in 7 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test VvvebJs?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1acbab7ebfe3. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test VvvebJs?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does VvvebJs take to install?
- 7.3 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 VvvebJs need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing VvvebJs?
- 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 VvvebJs?
- 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.