# 🎉 Node-RED 5 now available

**URL:** <https://discourse.nodered.org/t/node-red-5-now-available/101239>\
**Category:** News\
**Created:** [9 June 2026 09:29 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239 "2026-06-09T09:29:10Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [10 June 2026 11:02 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/26 "2026-06-10T11:02:49Z")

</div>

Another small issue with the script, or actually the service file. There should be a line defaulting NODE\_RED\_OPTIONS to an empty string  
`Environment="NODE_RED_OPTIONS="`

Without that line this warning is shown when the service is started  
`nodered.service: Referenced but unset environment variable evaluates to an empty string: NODE_RED_OPTIONS`

Possibly also take out the max\_old\_space node options at the same time, changing that line to  
`Environment="NODE_OPTIONS="`

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [11 June 2026 12:20 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/27 "2026-06-11T12:20:44Z")

</div>

Split this topic on 11 June 2026 12:20 UTC

5 posts were split to a new topic: [Issue with node-red-context-monitor and Node-RED 5](https://discourse.nodered.org/t/issue-with-node-red-context-monitor-and-node-red-5/101256)

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [10 June 2026 21:07 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/29 "2026-06-10T21:07:16Z")

</div>

1:  
I've read and like the sorting of the `link` nodes.  
By name not time made.

But one thing I think would be nice is a `find` option.

(Ok, I guess if they are sorted by name, _finding_ a link by name may be moot.)

2:  
The ~~`documents`~~ `help` option for a node.  
I am using a _new_ node and am not familiar with what it wants.  
I click on the node and open the ~~documents~~ `help` to see the stuff.

I then want to edit a `function` node (for example) to construct the required message format.

But as soon as I do that the `help` window changed to the `function` node's help.

It would be nice if you could _lock_ the `help` to the original node so you keep the new/useful/needed information visible as you are working in/on other nodes.

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [12 June 2026 08:05 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/30 "2026-06-12T08:05:32Z")

</div>

Using foreign plugins can cause hanging scrollbars:

![Screen Recording 2026-06-12 at 09.56.08](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/4/b/4b067bef8deb89f7b94cfa55d36b32c3bae2bd34.gif)

Here I've started NR5, the 'i' panel is shown by default. I switch to a foreign plugin panel (the layout in this case) and I then reload the browser. After reload, I'm left with a hanging scrollbar that then, when I select the 'i' panel, makes sense.

EDIT:

Another scrollbar related issue is that there seems to be no scroll bars for plugin content when the debug panel is opened:

![Screen Recording 2026-06-12 at 10.10.20](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/2/a2b7ad23441219b8347544f54c3ee0548abf7736.gif)

The debug panel is open and the top half is the plugin panel. For the inbuilt plugins, there is a scrollbar to scroll up and down, for the foreign ones there isn't a scrollbar (hard to see but I'm actually scrolling in the animation).

I assume this has to do with some HTML-voodoo ~~(some css class not being added to the divs). Are there new guidelines for creating plugins dialogs? Is there a go-to plugin that does this out of the box that one can copy?~~ Use `overflow-y: auto` on the outermost div.

EDIT2:

Added `overflow-y: auto` fix.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [12 June 2026 08:24 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/31 "2026-06-12T08:24:12Z")

</div>

> [@gregorius](#):
>
> Here I've started NR5, the 'i' panel is shown by default. I switch to a foreign plugin panel (the layout in this case) and I then reload the browser. After reload, I'm left with a hanging scrollbar that then, when I select the 'i' panel, makes sense.

I spotted this once (in last beta) but could never recreate it and assumed it was my baulked env (running from source with local inflight modifications) since it never came back.  
Now you have also witnessed this - something aint right.  
Can I trouble you to open an issue please? Include the steps and requirements to make it happen too.

Thanks.

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [12 June 2026 08:45 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/32 "2026-06-12T08:45:43Z")

</div>

Done: [NR5: Hanging Scrollbars when switching plugin panels and reloading browser · Issue #5802 · node-red/node-red · GitHub](https://github.com/node-red/node-red/issues/5802)

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [12 June 2026 10:28 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/33 "2026-06-12T10:28:56Z")

</div>

Ok, you got me - overall I have to say that the features of NR5 are nice - better zoom and having four different places for panels is great. It's a smidgen faster than 4 and that makes the overall experience a lot more snappy. (And bringing back the click-to-close-and-save feature - yeah!)

I'm just going through upgrading my plugins and overall, it's straight forward and no major headaches - most of my weird editor changes seem to be working as suspected.

Ironically this will probably make NR more over a dashboard than ever before 😉

Good job, level up! As they say ...

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [12 June 2026 14:30 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/34 "2026-06-12T14:30:40Z")

</div>

Split this topic on 12 June 2026 14:30 UTC

A post was split to a new topic: [Error when trying to add a custom sidebar tab](https://discourse.nodered.org/t/error-when-trying-to-add-a-custom-sidebar-tab/101267)

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [12 June 2026 14:21 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/35 "2026-06-12T14:21:07Z")

</div>

There has been a change to the [TreeList widget](https://nodered.org/docs/api/ui/treeList/):

![Screen Recording 2026-06-12 at 16.14.57](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/d/1d5b856c0c42bf6cdddafb9edbb4f5a91d47b631.gif)

It now takes a second click to open a list of children in the list. In NR4 (the orange highlight), one click does a highlight and expands the children list. In NR5 (blue highlight), that now takes two clicks: one to add the highlight and second click to expand the children list.

This is of course perhaps intended but it's still irritating since it feels wrong being used to the original behaviour.

(the animation didn't always capture the second click but its definitely there - animate gif conversion is to blame.)

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [12 June 2026 14:30 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/36 "2026-06-12T14:30:11Z")

</div>

There was a change to let a TreeList instance declare if it should expand on one or two clicks; when testing the Explorer sidebar, having it expand a flow's list of nodes when you were just trying to navigate it was unhelpful.

I _thought_ I had made the change opt-in - so existing treelists wouldn't have been affected. Can you raise an issue?

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [12 June 2026 14:47 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/37 "2026-06-12T14:47:28Z")

</div>

> [@knolleary](#):
>
> I _thought_ I had made the change opt-in

I'm using an old settings.js, i.e. a NR4 so I might not have that setting - if it's in the settings.js

> [@knolleary](#):
>
> Can you raise an issue?

Can do

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [12 June 2026 14:50 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/38 "2026-06-12T14:50:11Z")

</div>

> [@knolleary](#):
>
> I _thought_ I had made the change opt-in

I meant at the code API level - not user level.

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [12 June 2026 14:52 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/39 "2026-06-12T14:52:45Z")

</div>

> [@knolleary](#):
>
> I meant at the code API level

Ah ok, in that case _QED for me_ --\> Issue --\> [NR5: opening TreeList now takes two clicks by default · Issue #5803 · node-red/node-red · GitHub](https://github.com/node-red/node-red/issues/5803)

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [12 June 2026 17:06 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/40 "2026-06-12T17:06:12Z")

</div>

Sorry ... another bug perhaps:

![Screen Recording 2026-06-12 at 18.58.19](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/2/621a8a5934048712488ced36704aeb418b74c47e.gif)

Scrollbars don't update if iterating over nodes in the same flow tab. Here the scrollbar on the right should be updated when I iterate over search results _in the same tab_. I have the feeling that the scroll bars are only set correctly if the search results move _across_ flow tabs.

In the animation, need to keep an eye on the flow tab and the scroll bar on the right. Looking closely, the scroll bars are only updated if the tab is change. Even when moving across the flow, if it's the same tab, the scroll bars aren't updated.

EDIT:

also after a resize:

 ![Screenshot 2026-06-12 at 19.07.27](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/4/c/4c0d6e05297ec801f96f2fd476b22ee69838a7fe.png)

🙂

EDIT2:

In the palette manager:

 ![Screenshot 2026-06-12 at 19.35.15](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/f/5f2a269324584429e1fe09b8d82a5b4cb5f14227.png)

"0 plugins" should in fact be "1 plugin" - those packages that have plugins have zero of them and those that have no plugins, have just 1 or more nodes ....

---

<div class="post-metadata">

**Author:** ![PizzaProgram](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/pizzaprogram/32/19431_2.png) [@PizzaProgram](https://discourse.nodered.org/u/PizzaProgram)\
**Post date:** [13 June 2026 06:06 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/41 "2026-06-13T06:06:59Z")

</div>

> [@Vote for change. Debug "payload" only || or || the whole \`msg\`?](https://discourse.nodered.org/t/vote-for-change-debug-payload-only-or-the-whole-msg/101216/13):
>
> No. Node-RED 5 will refuse to run on anything prior to 22. There are simply too many security issues with old versions of dependencies that we had to move up the baseline.

In that case the editor should **not** notify users running prior Node.js v22 that :  
v5.0.0 is available.  
_(I've just got a popup like that after pressed Ctrl + F5 in my FFox.)_

Or at least it should not allow to try auto-update if it will fail anyway on pre v22 / Win7 .  
Is there any auto-failsafe test for that?

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [13 June 2026 07:29 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/42 "2026-06-13T07:29:57Z")

</div>

One more thing that I notice was that there is no longer a buffer between edge of workspace and edge of browser, NR4:

 ![Screenshot 2026-06-13 at 09.23.16](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/9/7/97a7ddf4c056eca30b58da65c4f8d70bce74e16d.png)

(ignore the image that happens to be attached to the node - this would also happen to nodes)

The same in NR5 then has the navigation helpers overlayed and also the scrollbars:

 ![Screenshot 2026-06-13 at 09.20.30](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/3/63908e03077b4de993afb01b6eed36df61b890e0.png)

I know this is an edge case but it basically means that of the 8000x8000, about 50 px bottom and to the right are non-usable. Any content located at the very bottom or very right will have the scrollbars going over it.

If the controls (i.e. scrollbars and navigation helpers) would simply disappear (much like the dock on macos that can hide by itself) then this is won't be an issue.

---

<div class="post-metadata">

**Author:** ![RoustamManookian](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/roustammanookian/32/68896_2.png) [@RoustamManookian](https://discourse.nodered.org/u/RoustamManookian)\
**Post date:** [13 June 2026 07:38 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/43 "2026-06-13T07:38:40Z")

</div>

The best feature that I was waiting for is the "Debug pause". Thanks !!!

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [13 June 2026 08:01 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/44 "2026-06-13T08:01:06Z")

</div>

Not sure if this has been reported before.

With the left hand sidebar visible, edit a function, open the extended editor. It overlays the sidebar.

Now when the mouse is positioned over the right hand edge of the sidebar, the cursor changes to the left/right arrow & clicking/dragging no longer selects text in the editor.  
Instead it resizes the underlying sidebar.

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [13 June 2026 09:45 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/45 "2026-06-13T09:45:12Z")

</div>

You must call `RED.plugins.registerPlugin(...)` to register a plugin.

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [13 June 2026 10:07 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/46 "2026-06-13T10:07:29Z")

</div>

> [@GogoVega](#):
>
> `RED.plugins.registerPlugin(...)`

Ah ok, so there is a difference between sidebar, plugins and nodes (config & workspace)? But why does it show "0 plugins" at all, for example, tarball does not have a sidebar nor plugin and nothing is shown:

 ![Screenshot 2026-06-13 at 11.54.34](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/8/386e29fc8acf7abaf8b57457ed77bc77eafb456a.png)

NodeDev has a plugin directory and in that directory there is a sidebar defined (which is also shown as a sidebar). In the package.json it's declared as a plugin but in fact there are [two](https://github.com/gorenje/node-red-contrib-nodedev/blob/30318b84966f0186caeed3d5992c5b7705dac03f/package.json#L33-L35) plugins defined - one is just init code.

Indeed `registerPlugin` isn't called by NodeDev, instead a [`RED.sidebar.addTab`](https://github.com/gorenje/node-red-contrib-nodedev/blob/30318b84966f0186caeed3d5992c5b7705dac03f/plugins/node-factory-sidebar.html#L144C6-L153C10) is called.

[Previous page](https://discourse.nodered.org/t/node-red-5-now-available/101239.md?page=1)

[Next page](https://discourse.nodered.org/t/node-red-5-now-available/101239.md?page=3)