// the find
TotallyInformation/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.
UIBUILDER is a Node-RED node that bridges flows to a real front end — Socket.IO data exchange, no-code/low-code widget config, or full-code HTML/CSS/JS you own completely, all in one package. It's for Node-RED users who've outgrown Dashboard 2 and want an actual web app without leaving the flow editor, but don't want to stand up a separate Express/React stack.
Genuinely framework-agnostic — you can ship vanilla HTML/CSS/JS or wire in Vue/Svelte/React, and the repo even maintains a separate example Svelte template to prove it. Front-end tooling is current (ESBuild + LightningCSS builds, IIFE and ESM bundles) rather than a Node-RED node stuck on ancient browserify output. Has its own standalone sub-libraries (ui.js for turning JSON into HTML, a web-components library with its own docs site) that work independently of Node-RED, so logic isn't trapped behind the node. CodeQL, Dependabot, and OpenSSF Scorecard are all wired into CI, which is more security hygiene than most Node-RED contrib packages bother with.
Single maintainer (Julian Knight) for a project with 7 major versions and this much surface area — nodes, a client runtime, admin APIs, a router library — is a real bus-factor risk for anyone building on it long-term. Socket.IO as the transport is a heavier dependency than plain WebSockets for what's often simple msg-passing, and it shows up in the contributor list as the source of at least one 'complex async bug' that took a dedicated PR to fix. Breaking changes are tied to Node.js/Node-RED baseline bumps (v18→v24 already flagged for contributors), so upgrading across majors means reading changelog diffs across CHANGELOG, CHANGELOG-v5, v6 archives etc. — not a clean migration story. Entirely Node-RED-specific; none of this transfers if you ever move off the flow-based-programming model, unlike a standalone framework choice would.