🎉 Node-RED 5 beta 2 now available

:tada: The second beta release of Node-RED 5 is now available!

After a short break for the Christmas period, we're back to our regular scheduled beta releases of Node-RED 5

We're continuing to iterate the UI appearance towards the concept designs in the original issue. The most obvious change here being the restyled header.

We've also addressed some of the feedback/issues with the previous beta; it should now remember the layout changes you make with the sidebars, and some issues with the resizing of the panels have been fixed.

This release also includes two new features:

Pausing debug output

A long requested feature, it is now possible to pause the debug sidebar using a toggle button in the sidebar header. Whilst paused, it stops scrolling and any new messages received are dropped.

Delay node - burst mode when rate limiting

The default behaviour of the Delay node's rate limiting mode has always been to spread out the incoming messages evenly to the rate configured in the node. The node can now also be put into burst mode; where it will allow messages through at whatever rate they arrive at until the limit is reached - at which point it will block the messages until the start of the next time interval.


Installing the beta

If you want to try out the beta, you will need specify node-red@next when you use npm to update. Without the @next you'll still get 4.1.x

So on a Pi you'd do:

sudo npm install -g --unsafe-perm node-red@next

Docker images

The beta images will be available soon - all being well with Ben on holiday. They will be available under nodered/node-red-dev:v5.0.0-beta.2 - with the default image being based on Node 24.

Reporting problems

If you hit any problems, please report them either as a reply on this topic, or in the #core-dev slack channel. Please do not post new topics to the forum regarding the beta as that could confuse users who are not using the beta.

What's Next

The Node-RED 5.0 work is being tracked in this issue. From there you'll find sub-issues for the various strands of activity going into Node-RED 5.

For the UX updates, you can follow this issue - with a number of sub-issues already raised for the next betas to address.

We're going to revisit some of the sidebar changes. There's a concern that the horizontal space used by the button bars isn't good use of the space - and reduces the available workspace size.

The header has been restyled, but there are some functional changes to come. For example, moving the main menu to the Left-hand corner rather than the right and having a more standard search behaviour. As mentioned in the last beta, we also need to rework some of the menu contents to reflect the sidebar changes.

We also want to make sure each beta contains more than just theme changes - and there are still plenty of PRs to work through.

8 Likes

A big yes on the debug pause. Most definitely glad to see that

3 Likes

I noticed a strange behavior if you un-split the sidebars and refresh the browser.

Initial state.

Un-split the sidebars.

After refreshing.

Weirdly, having upgraded from the previous beta, I can't see the debug output at all?

OK, strange after a 3rd reload, this time with the browser debug tools open, it finally appeared.

If you untick either icon in left pane BOTH sidebar contents disappear.

On the right hand side unticking debug icon removes all panes, clicking on any other icon reinstates the debug pane plus pane related to icon clicked.

Yes, that is the current implementation. As I note in my post above, we're rethinking the sidebar buttons, so behaviours/design are all subject to change.

Please, are you reverting back the changes to escaping from edit node box???

Please please please.

4 Likes

Yes. Currently considering a PR (Add several click-outside-edit-tray behaviors by GogoVega · Pull Request #5385 · node-red/node-red · GitHub) that adds an option - or whether we should just be opinionated and revert behaviour the way we always did with very little complaint.

2 Likes

Is there any plan to redesign or improve the information shown after importing a flow or an example flow, so that it does not cover the flows tabs?

It isn't something that has been specifically raised as a concern. The notification can be clicked on to dismiss it, and ultimately has to appear somewhere. If you have any suggestions for improvements, please do share.

1 Like

Since the flows tabs will be positioned higher, could the import message simply be displayed below them? In my opinion, additional required clicks slow down the workflow.

1 Like

Having moved the debug output up to the top RH pane, is there a way of removing the now empty bottom RH pane?

By the time we're done, it will all work flawlessly and intuitively. Until then, quirks may exist.

Understood, just checking whether I had missed something.

One thing that continually frustrates me in the UI is that if I search for unused config nodes and select one and hit the delete key then it deletes it, and leaves another one highlighted. However, if I want to delete that one too then I have to click it again, hitting delete again does not delete the highlighted node.
This is a common situation particularly using the flowfuse dashboard, as after importing a flow from the forum to replicate an issue, and then deleting that flow, often there is a group, page and theme all to delete. Deleting the group conveniently leaves the page highlighted, but I have to click it again, and again ...

1 Like

That is annoying and should be fixed. If there is not already an open issue, please do open one Colin. Sounds like a candidate for a good-first-issue label!

PS, I dont think that is purely a NR5 issue right?

Is that not a deliberate thing to prevent accidental deletion due to too many key presses ?

And you can also delete several at once. Or is this really a bug?

Actually it would be my 39th issue on the core.

In attempting to replicate the issue in sufficient detail for an issue it seems that something has changed in v5 so I am just investigating that.