node-red-contrib-uibuilder 5.1.1

Easily create data-driven web UI's for Node-RED using any (or no) front-end library.

npm install node-red-contrib-uibuilder

NPM Version NPM Total Downloads NPM Downloads per month GitHub last commit GitHub stars GitHub watchers GitHub license Min Node Version Package Quality DeepScan grade CodeQL Open Issues Closed Issues

Please Note that:

  • v5.0.0 is a very large change and has breaking changes from v4.1.4, please see the CHANGELOG for details.
  • Node.js v12.20 and Node-RED v1.3+ are required.
  • uibuilder follows semantic version numbering - as such, each major number change indicates breaking changes and you should review them carefully before installation.

Older changes can be found in the previous change documents: CHANGELOG-V3/V4, CHANGELOG-v2, and CHANGELOG-v2


A Node-RED web user interface builder. uibuilder aims to provide an easy to use way to create dynamic web interfaces using any (or no) front end libraries for convenience.

uibuilder is rather the opposite of Node-RED's Dashboard. Whereas Dashboard is designed to make it very easy to create a UI but trades that off with some limitations, uibuilder is designed to let you do anything you can think of with any framework (or none) but at the trade off of having to write your own front-end code.

uibuilder should generally also be a lot faster and more resource efficient in use than Dashboard though that obviously depends on what front-end libraries and frameworks you choose to use.


The purpose of uibuilder is to:

  • Support an easy method for creating and delivering data-driven web apps.
  • Be a conduit between Node-RED and a front-end (browser) UI web app.
  • Be UI framework agnostic. While VueJS is often used with uibuilder, it isn't a necessary dependency. Indeed no framework will be needed to use uibuilder.
  • Provide interface/data standards for exchanging data and controls with the UI.

Core features

  • Provide a 2-way communications channel between the Node-RED server (back-end) and front-end UI code.
  • Provide a Node-RED node to act as the focus for communications.
  • Provide a front-end library to do the complex parts of the communications.
  • Provide templates for front-end code to enable people to get a quick start on creating web apps.
  • Allow management and serving of npm packages that provide front-end libraries consumable easily by front-end code.
  • Allow editing of front-end code (designed for small changes, use web development tools generally).

Future direction

The general direction of uibuilder (or associated modules) is likely to include:

  • An extensible security model.
  • A set of extension front-end components with well defined (reusable) data schemas for doing common UI tasks. The defined data schema's would cover both the component content and configuration data so that both could be sent from Node-RED via uibuilder and any return data structures would similarly be well defined.
  • A capability to have configuration-driven (data-driven) UI's. Creating a framework for describing a UI and translating to actual code.
  • A UI designer allowing users without HTML/CSS/JS skills to create reasonable web apps without code.

Feature details

The key features and benefits are: (Click to show/hide)
  • Designed as an alternative to the Node-RED official Dashboard. Without the overheads and restrictions.
  • Control everything from the Node-RED admin ui. Edit your front-end resource files, manage front-end packages. No need to access the servers command line.
  • Manage startup templates. Internal templates for VueJS and bootstrap-vue in addition to a plain template are available. Load templates from other repositories via degit. Makes it easy to share templates that provide a whole app or just deal with boilerplate.
  • Have as many custom user interfaces as you want. Just 1 node is needed for each entry point. Use link nodes to send data from other parts of your flows.
  • Has a control interface separate to the message interface. Know when a browser connects or disconnects, send cached data.
  • Can be a lot lighter in weight and more mobile friendly than the Node-RED official Dashboard.
  • Use any front-end framework you like. Simply install via the built-in library manager.
  • Use without any front-end framework if you prefer. Keep it light and simple. Try this out with the "Blank" template.
  • The included front-end library (uibuilderfe) provides connectivity to Node-RED and msg event handling.
  • Write your own HTML, CSS and JavaScript to define the perfect front-end user interface for your needs.
  • Edit your custom front-end code from within the Node-RED Editor. Auto-reload your clients on changes to the code. Great for rapid development. Note that this is designed for quick edits, it is recommended to use your normal web development toolchain for larger edits.
  • Needs almost no boilerplate in your front-end code in order to work.
  • Optional index web page listing of available files.
  • Two detailed admin info web pages are included to help authors understand where everything is and what is available.
  • Uses Node-RED's own ExpressJS webservers by default. Switch to a custom ExpressJS server if desired.
  • Has middleware for ExpressJS (for web services) and Socket.IO (for communications, both at initial connection and per-message) so that you can add your own custom features.
  • Can create custom API's for each uibuilder instance.
Current limitations are:
  • You have to write your own HTML, uibuilder doesn't (yet) do it for you. This is by design. I hope to have a component design available at some point which will give additional options and make the UI building easier.

  • You have to know the front-end library locations for installed libraries and edit your HTML accordingly. The uibindex admin API (accessible from any node's admin ui) shows you all of the root folders and what the package authors report as the main entry point for all active packages. There is now also a simplified information page for the currently viewed uibuilder node instance, this is access from a button in the configuration panel.

    Note that this is a limitation of npm and module authors, not of uibuilder. Unless module authors correctly identify the browser entrypoint for their libraries, uibuilder can only guess.

  • You cannot yet compile/compress your custom front-end code (HMTL, JS, SCSS, etc.) for efficiency. This will be added soon.

    This will use a local package.json file that contains a "build" script. If it exists, uibuilder will expose a build button that will run the script.


1. Additional Documentation

Most of the detailed documentation is moving into the Technical Documentation. This can be accessed on the GitHub pages site. Or from the button in the Node-RED Editor's configuration panel for any instance of the uibuilder node (url <node-red-editor-url>/uibdocs/). You will find the raw versions in the docs folder of this package.

There is some more information and some examples available in the GitHub WIKI.

Also, don't forget that there are example flows built into the Node-RED library that you can import into your flows. And uibuilder has its template feature that lets you load example front-end code.

2. Getting Started

If this is all new to you, please do take a look at the first-timers walkthough of using uibuilder. It aims to take you through, step-by-step, installing uibuilder and creating your first simple web app. If you have any difficulties, please feel free to ask questions on the [Node-RED forum](Latest node-red-contrib-uibuilder topics - Node-RED Forum (

2.1. Install

To install the current live version, please use Node-RED's Palette Manager.

To install a specific uibuilder development or test branch from GitHub, use npm install TotallyInformation/node-red-contrib-uibuilder#<BRANCH-NAME> from the command line on the server, having first changed to the userDir folder (normally ~/.node-red). If you just want the main branch which contains the latest development build, you can do npm install TotallyInformation/node-red-contrib-uibuilder

To install a specific release from npm, use npm install [email protected]<VERSION>. In addition to release versions (e.g. 1.2.2), you can also use latest and v1-last. Sometimes, next may also be available. Check out the Versions tab on the npm site for available versions.

2.1.1 Installing front-end libraries

You may also want to install some front-end libraries. In particular, you will need to install VueJS and bootstrap-vue if you want to use the various VueJS templates. You should do this using uibuilder's library manager.

As of v5, front-end libraries will be installed into the <uibRoot> folder. By default, this will be ~/.node-red/uibuilder/. If migrating from v4 to v5, you will need to reinstall libraries. You can then remove the previous versions from your <userDir> folder. It is possible to manually install front-end libraries if you wish. The <uibRoot>/package.json file contains additional details regarding the packages that are installed, this is updated automatically.

If installing manually, you may need to restart Node-RED.

2.2. Simple flow

Once installed,

  1. add a simple flow consisting of a trigger, a uibuilder and a debug node all connected in order.
  2. Change the url setting of the uibuilder node to something valid.
  3. Deploy the changes then
  4. double click on the uibuilder node,
  5. click on the web page url.

That will show you a simple page that will show you a formatted view of any msg send from Node-RED into the node. No additional libraries or frameworks are needed for that. The only dependencies are to load the uibuilderfe.js library, start the library using uibuilder.start() and then create a listener for incoming messages. This uses the default Blank template.

2.3. Edit the source files

From the node's configuration panel in the Editor, click on "Edit Source Files" to see the front-end code. Make some changes to see what happens.

If you need more space for the editor, click on the button underneath the text editor. To get back, press the same button (which is now highlighted) or the Esc key.

Click on the Save button to save changes, Reset to revert to the saved file, Close to exit the editor. Note that the close button isn't available while there are outstanding changes, press Save or Reset first. The Editor's red Done button is also disabled while there are still outstanding changes.

You can create a new file and delete files and folders as well with the appropriate buttons. If you delete one of the default index.(html|css|js) files and have the Copy Index flag set (in advanced settings), the file will be replaced automatically with the default template file. Useful if you get into a complete mess.

2.4. Install additional front-end libraries

Click the "Manage front-end libraries" button. Then click the + add button and type in the name of the package as it is defined in npm.

You can also remove installed libraries from here.

The uibuilder Detailed Information API page (link in the configuration panel) shows details of all packages installed, their URL for your html pages and their physical location on the server (so that you can track down the right file to include in your HTML).

2.4.1 Using VueJS

If you want to use the VueJS based templates, you will need to install vue and bootstrap-vue libraries.

The included VueJS, bootstrap and bootstrap-vue templates make for a really easy to use initial setup that is very easy to use but powerful to build any kind of web user interface. The template files should give you some ideas on how to use everything.

back to top

3. Features

  • A single node is used to define an end-point (by its URL path). The node can be included in flows as many times as you like - but each instance must have a unique URL path name.

  • Each node instance gets its own Socket.IO namespace matching the URL path setting. Note that Socket.IO will efficiently share sockets while keeping traffic separated by namespace.

    The namespace is the uibuilder url (defined in the Editor) with a preceding "/".

  • There is a front-end library uibuilderfe.min.js or uibuilderfe.js that hides all the complexities of using Socket.IO so that your own FE code is easy to write. It provides a simple event handling system so that you can subscribe to changes and process them as they happen. The default index.js file has details and examples of use. The library is written so that it can be sourced via html or included via a build step (e.g. webpack).

    Initialise the library with:


    Handling incoming messages from Node-RED is as simple as:

    uibuilder.onChange('msg', function(msg){'[uibuilder.onChange] property msg changed!', msg)

    Sending a message back to Node-RED is a simple as:

    uibuilder.send( { 'topic': 'from-the-front', 'payload': 42 } )
  • npm packages can be installed (or removed or updated) using the node's admin ui in Node-RED. This allows you to manage the availability of front-end libraries very easily. No need to have access to the servers command line. Any front-end library that is available as an npm package can be managed this way. Installed packages will be made available to your web app.

  • Typically, very little code is needed to create a simple, data-driven web UI. The node's module contains default html, JavaScript and CSS master template files that are copied to your local src folder for you to edit as required. It gives you a simple to follow template that kick-starts your web app development. Additional templates are available (even external ones can be used) that help kickstart your development.

  • Including a _socketId attribute on messages sent from Node-RED will send to that ID only.

    Note that an ID is associated with a specific browser tab and is reset when the page is reloaded or if the page temporarily looses connection.

    The _socketId attribute is added to any msg sent from the client to Node-RED. See the WIKI for more information.

  • A second output port gives access to some control messages.

    This allows additional processing when a client connects or disconnects, an instance is (re)deployed or there is a socket error.

    A common use for this is to send cached information back to a newly connected client (or one that has had the page reloaded).

    Other uses could include outputing some standard information when a new client connects. Or you could use the information to keep utilisation metrics.

    See the Pre-defined Messages page in the Tech Docs for details.

  • On deployment of the first instance of uibuilder, a new folder is created within your Node-RED user directory (typically ~/.node-red) with a fixed name of uibuilder.

    If you are using Node-RED's projects feature, the folder will be created within your project folder instead.

    From v4.0.0, you can change the location of this <uibRoot> folder by specifying a location in Node-RED's settings.js file.

    /** Custom settings for all uibuilder node instances */
    uibuilder: {
        /** Optional uibRoot folder. 
         * By default, uibuilder will use `<userDir>/uibuilder`
         * Use this setting to change that.
        uibRoot: process.env.UIBROOT || '/where/i/want/it',
  • On deployment of any new instance, a new sub-folder within uibuilder is created.

    The name is the same as the URL path specified in the node instance's settings. (defaults to uibuilder). src and dist sub-folders are also created. The url name is limited to a maximum of 20 characters and cannot be templates as this is reserved.

    The files in these folders can be edited from within the node's configuration panel in Node-RED's Editor. No need for command line or other file access on the server.

    If you remove the node from your flows, Node-RED will offer to delete the folder as well. If you change the url, Node-RED will try to rename the folder.

  • You can serve your front-end files from one of two locations within your <uibRoot>/<url>/ instance folder. Either the src or dist folders. Mostly you will stick with the default src folder and write your code there. However, if you need a "build" step for any reason, you will probably want to switch to the dist folder which should be the target of your build process.

  • Any resource (html, css, js, image, etc) placed within the dist/src sub-folder is available to the browser client. The default URL would be http://localhost:1880/<url> (where the path is set as per the point above). That URL will load index.html. Resource URL's take the httpNodeRoot Node-RED setting into account.

  • An additional "common" folder is created in the uibuilder root folder (e.g. ~/.node-red/uibuilder/common)

    This is made available to each node instance and is used to make common resources available to multiple web apps.

    See the URI Paths page in the WIKI for details of all URI's available to your web apps.

    Better still, see the uibuilder details and instance details buttons in the uibuilder configuration panel in the Node-RED Editor, these will show pages of more detailed information.

  • You can use a separate webserver from the Node-RED internal webserver by specifying a port in settings.js

    ** The main purpose of this is that it lets you use a reverse proxy to securely expose only uibuilder's endpoints without exposing Node-RED itself.** It also gives you more control over headers and other settings.

    It will still use Node-RED's Admin server but your own front-end code and all of the installed vendor packages and middleware (including Socket.IO) will now use a separate http(s) server and ExpressJS app.

    If you specify https for Node-RED, your custom server will also use https and will automatically pick up the certificate and key files from settings.js. You can override this using the uibuilder settings in settings.js.

    NOTE: That all instances of uibuilder nodes will all use the same webserver. Allowing multiple servers requires a significant development effort but is on the backlog (just a very long way down).

    To use a different webserver, you have to add the following into the module.exports part of your settings.js file:

      /** Custom settings for all uibuilder node instances */
      uibuilder: {
          /** Optional HTTP PORT. 
           * If set and different to Node-RED's uiPort, uibuilder will create
           * a separate webserver for its own use.
          port: process.env.UIBPORT || 3000,

    Note that the above will let you use an environment variable called UIBPORT to set the port. This must be done before starting Node-RED. The port setting is not dynamic.

  • Some visual helper functions are now included with the front-end library. The idea being to bridge the complexity gap between the Node-RED Dashboard and uibuilder for novice front-end programmers. See the technical docs for details.

    Initially there is a "toast" feature which overlays notifications on your UI. You can trigger from within your front-end code or you can send a specifically crafted message from Node-RED to trigger toasts.

back to top

4. Known Issues

These are things to be aware of & that I'd like to tidy up at some point.

  • v5 does not have a completely working security model. It is not fully tested and may not work. Do not use this part in production. Everything else is fine.

  • Some of the VueJS helpers in the front-end library have edge-cases where they don't work.

  • Socket.IO isn't secured by default Use uibuilder's ExpressJS and socket middleware feature to secure things properly before considering use over the Internet. ALWAYS configure TLS before configuring authentication. If Node-RED is using HTTPS, Socket.IO will also use HTTPS/WSS encryption of traffic.

    Note, however that the socket middleware is only called on initial socket connection. Once the connection upgrades to websocket, this is no longer called.

    I hope to improve this in a future release.

    You could also work around this by using a proxy such as NGINX or HAproxy to be the TLS endpoint. Just make sure you proxy the websocket traffic as well as the standard web traffic.

    See the security documentation for more information.

Node-RED Flows Library Scorecard

The scorecard for uibuilder shows a number of minus points. However, it should be noted that these are somewhat spurious.

  • Node.js Version - at the time of writing, Node-RED v2.2 states that Node.js v12.0 is the minimum version whereas uibuilder states v12.20. This is because there are some serious bugs and issues in versions of node.js less than v12.18 or so. Specifically, you cannot use dynamic imports on <12.20.0. Really, Node-RED v2.0 should have increased its minimum supported node.js version.
  • Number of Dependencies - Scorecard marks this as a warning. However, uibuilder does a LOT for you and so has a higher than average dependency on external modules. At 14, this is still less than some other Nodes. For example, node-red-dashboard shows as only 4 dependencies but really has 28! They don't show because they have been compiled in so only appear as dev dependencies.
  • Dependencies use latest versions - uibuilder has a single dependency that does not track current releases. This is execa. The latest releases of which only work as a node.js ECMA module. To use this would require significant rewrites of most of uibuilder which isn't feasible. As soon as Node-RED moves to a version of node.js that has a minimum support of node.js v12.20 or above, dynamic imports will work and at that point, execa can be updated because dynamic imports allow an ECMA Module to be called from a CommonJS module.

back to top

5. Discussions and suggestions

The best place to ask questions about uibuilder is the Node-RED Forum.

Alternatively, use the GitHub issues log for raising issues or contributing suggestions and enhancements and the GitHub Discussions page for general questions, suggestions, etc.

Please note that I rarely have time to monitor the #uibuilder channel in Slack any more, it is best to use Discourse or raise an issue.

I do occasionally try to look out for uibuilder related questions on Stack Overflow but again, time does not always let me do this.

6. Contributing

If you would like to contribute to this node, you can contact Totally Information via GitHub or raise a request in the GitHub issues log.

Please refer to the contributing guidelines for more information.

7. Developers/Contributors

Many other people have contributed ideas and suggestions, thanks to everyone who does, they are most welcome.

profile for Julian Knight on Stack Exchange, a network of free, community-driven Q&A sites

Please also check out my blog, Much Ado About IT, it has information about all sorts of topics, mainly IT related, including Node-RED.

back to top

Node Info

Version: 5.1.1
Updated 5 months, 2 weeks ago
License: Apache-2.0
Rating: 4.7 27




733 in the last week


  • node-red
  • ui
  • gui
  • dashboard
  • spa
  • web
  • website
  • data-driven
  • webpage



  • Julian Knight
  • Colin Law
  • Steve Rickus
  • Ellie Lee
  • Thomas Wagner
  • Arlena Derksen
  • cflurin
  • Scott Page - IndySoft
  • Stephen McLaughlin - Steve-Mcl
  • Sergio Rius
  • Thorsten von Eicken
  • meeki007
  • talltechdude