node-red-contrib-uibuilder

Easily create data-driven web UI's for Node-RED. Single- & Multi-page. Multiple UI's. Work with existing web development workflows or mix and match with no-code/low-code features.

Runssource: GitHubhomepageJavaScriptApache-2.0commit f9066f0f6a06

JavaScript, Apache-2.0 licensed. The project labels itself: css, dashboard, data driven, flow based programming, html, javascript, low code and no code.

node-red-contrib-uibuilder runs. An Argusic agent installed it in 34.3 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

A user install of node-red 4.1.16 + node-red-contrib-uibuilder 7.7.4 runs Node-RED, registers all 11 uibuilder node types with no errors, serves /testui/ and the client library with HTTP 200, and answers live Socket.IO control messages; the telemetry integration suite passes 24/24 against a schema-correct mock.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$1.24 (measured)
recorded runs
1
last tested
stars
529
forks
92
open issues
0
watchers
22
size
31 MB
created
last push

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.

Time lost to each failure while testing node-red-contrib-uibuilder, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Node 18.19.1 + jsdom 29/undici 7/parse5 8: ERR_REQUIRE_ESM and missing File/ArrayBuffer.resizable break require('jsdom') (uib-html node fails to load)18 minutes
  • wrangler 4 requires Node 22 and real Cloudflare creds for remote D1; local D1 ran but worker returned 500 (no schema) then 401 (no STATS_TOKEN secret)7 minutes
  • uibuilder 'get page meta' control handler crashes on deployed node: path.join(undefined) because sourceFolder was left undefined6 minutes
  • npm install and build succeeded but installed package could not build: ERR_MODULE_NOT_FOUND esbuild in bin/build.mjs (esbuild is devDependency, excluded from published tarball)5 minutes
  • Socket.IO polling transport fails against this server (xhr poll error) on Node 184 minutes
Install time
34 minutes
Cold machine to finish
36 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
curl admin:/testui:/uibuilder.iife.min.js all returned 200; socket.io handshake 200; websocket control roundtrip returned 'client connect' and real 'get page meta' file stats; npx vitest run returned 24 passed (24); repo npm run build printed '[build] Build complete.'
Model tokens used
6,123,948
Exact commit tested
f9066f0f6a06
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.

2026-10-18T22:51:27.087735Z ERROR codex_core::session: failed to record rollout items: thread 01a15…
tokens used
6,123,948
Everything is verified, errors are recorded, and fixes are applied. Final state and report below.
**Observed facts**
- `npm install` (repo root): added 1141 packages, exit 0.
- `npm run build` (repo root): `[build] Build complete.`; fe/node/CSS/docs bundles built.
- Node-RED 4.1.16 + this package (tarball install into `~/.node-red`): ran `node red.js`; log shows…
- HTTP verification: `/admin/` 200, `/testui/` 200 (serves template `index.html`), `/uibuilder/uibu…
- Live Socket.IO roundtrip (websocket, namespace `/testui`): runtime sent `client connect` control …
- Telemetry suite: `npx vitest run` against my schema-correct mock: **24 passed (24)**, exit 0.
- Errors fixed (each with a fix + time below); Node-RED runtime stays up under a respawn loop and a…

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 5 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.

What did not, or is not known

  • Took 34.3 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 5 css projects Argusic has installed and timed, node-red-contrib-uibuilder was the 5th fastest to reach a running state, and 4 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.001.24

Topics (from GitHub)

cssdashboarddata-drivenflow-based-programminghtmljavascriptlow-codeno-codenode-reduiweb-appweb-applicationweb-componentswebappwebsitewebsocketszero-code

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/node-red-contrib-uibuilder.svg)](https://argusic.com/subject/node-red-contrib-uibuilder)

Questions

Does node-red-contrib-uibuilder run?
Yes. node-red-contrib-uibuilder runs. Argusic installed and launched it on a clean machine in 34 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test node-red-contrib-uibuilder?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit f9066f0f6a06. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test node-red-contrib-uibuilder?
The run that produced this verdict cost $1.24: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does node-red-contrib-uibuilder take to install?
34.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 node-red-contrib-uibuilder need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing node-red-contrib-uibuilder?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does node-red-contrib-uibuilder compare with the alternatives?
Of the 5 css projects Argusic has installed and timed, node-red-contrib-uibuilder was the 5th fastest to reach a running state, and 4 of 5 reached one at all.
Where is the evidence for node-red-contrib-uibuilder?
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.

Discussion