# 🎉 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:** 13\
**Page:** 5

<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:** [23 July 2026 08:53 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/88 "2026-07-23T08:53:08Z")

</div>

I keep expecting to find a little `X` button on the titlebar of each side panel.

I'm looking at the panel thinking "I don't want to see that just now", then to close it I have to switch attention to the buttons at bottom right and work out which button is for which panel.

---

<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:** [23 July 2026 08:57 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/89 "2026-07-23T08:57:59Z")

</div>

> [@jbudd](#):
>
> I keep expecting to find a little `X`

That and the overlap on the right side with searched-for nodes being hidden under that sidebar so that I end up looking all over and then remove the side bar to finally find the node that was found.

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [23 July 2026 09:18 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/90 "2026-07-23T09:18:43Z")

</div>

I've not noticed this - I have info above debug - if I move info to left side - debug stays where it is at bottom right  
Before dragging

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/9/d9ee76261b24951812e6bbd9806f78e3201c0d9d.png)  
After dragging info to left  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/0/106746dbb105e3c682a820984802b8669b5e81ce.png)

---

<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:** [4 August 2026 15:53 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/91 "2026-08-04T15:53:13Z")

</div>

> [@gregorius](#):
>
> That and the overlap on the right side with searched-for nodes being hidden under that sidebar

For those facing this too, I've just testing this bit of JS

```js
RED.events.on("search:open", () => {
    $($('.red-ui-sidebar-right').find('.red-ui-sidebar-section-bottom')).fadeOut(500)
    $($('.red-ui-sidebar-right').find('.red-ui-sidebar-section-top')).fadeOut(500)
})

RED.events.on("search:close", () => {
    $($('.red-ui-sidebar-right').find('.red-ui-sidebar-section-bottom')).fadeIn(500)
    $($('.red-ui-sidebar-right').find('.red-ui-sidebar-section-top')).fadeIn(500)
})

```

which hides the sidebar when the search dialog is opened and unhides the sidebar when the search dialog closes again:

![Screen Recording 2026-08-04 at 17.48.50](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/9/298a13f235c7639fcdcc24aba1f63d3516c79096.gif)

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [24 August 2026 04:35 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/92 "2026-08-24T04:35:15Z")

</div>

When using a http request node with a binary buffer i noticed that the status remains on 'requesting' (not a browser issue? both chrome/safari show it even after quitting the browser and reopening node-red)

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/8/884d5e7cbda59e028a33bc6320a7392b5a63b73f.png)

---

<div class="post-metadata">

**Author:** ![gerrybartley](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerrybartley/32/67495_2.png) [@gerrybartley](https://discourse.nodered.org/u/gerrybartley)\
**Post date:** [24 August 2026 06:51 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/93 "2026-08-24T06:51:34Z")

</div>

I've seen that issue too but I'm using Node-Red 4.1.2 in my production environment

---

<div class="post-metadata">

**Author:** ![DWoodlock](https://avatars.discourse-cdn.com/v4/letter/d/49beb7/32.png) [@DWoodlock](https://discourse.nodered.org/u/DWoodlock)\
**Post date:** [1 September 2026 13:03 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/94 "2026-09-01T13:03:06Z")

</div>

I also experience this “requesting” status display in 4.1.1

Have confirmed the node is posting as intended, just the stays display seems to hang up.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [1 September 2026 17:45 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/95 "2026-09-01T17:45:46Z")

</div>

Hi @bakman2 - do you have a simple example I can test with ? Thanks

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [2 September 2026 04:58 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/96 "2026-09-02T04:58:28Z")

</div>

The plot thickens, this is weird.

The http req node remained in that 'requesting' state - it was fed into a function node that uses an external npm lib - disconnected the function node, deploy, requesting state gone, reconnected it and 'requesting' now behaves normally.

ie. i cannot reproduce it. Does the http request node 'care' about the result of the next node ?

---

<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:** [2 September 2026 10:23 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/97 "2026-09-02T10:23:52Z")

</div>

> [@bakman2](#):
>
> Does the http request node 'care' about the result of the next node ?

I'm sure it would be a bug if it did since nodes aren't really supposed to be dependent on what happens downstream.

I suspect that you hit a timing issue where the request timed out before the response was recieved?

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [3 September 2026 08:05 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/98 "2026-09-03T08:05:05Z")

</div>

looking at code there do seem to be some "holes" where status may not get cleared. Will take a deeper look later.

---

<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:** [3 September 2026 08:42 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/99 "2026-09-03T08:42:54Z")

</div>

> [@dceejay](#):
>
> "holes" where status may not get cleared.

I think I had this because Node-RED actually crashed and never sent the clear status call.

EDIT:

Ok, turns out it was a probably an endless loop that causes non-responsiveness in NR. So NR didn't really crash but just staled. I can reproduce this using this bit of code in the node:

```js
module.exports = function(RED) {
  function CorecrasherFunctionality(config) {
    RED.nodes.createNode(this,config);

    var node = this;
    var cfg = config;

    node.on('close', function() {
      node.status({});
    });

    /* msg handler, in this case pass the message on unchanged */
    node.on("input", function(msg, send, done) {
        node.status({ fill: "green", shape: "ring", text: "Requesting" });
        setTimeout( () => {
          node.status({});
        },3000)

        // this enters an endless loop that eventually crashes NR
        setTimeout( () => {
          while (true) {
            setTimeout(() => { }, 0)
          }
        },1000)
    });
  }

  RED.nodes.registerType("crasher", CorecrasherFunctionality);

}

```

this will eventually cause this:

```auto
node-red-empty500-1 | <--- Last few GCs --->
node-red-empty500-1 |
node-red-empty500-1 | [7:0xffffa0950000] 32633 ms: Scavenge (interleaved) 4047.6 (4065.9) -> 4047.6 (4112.9) MB, pooled: 0 MB, 15.98 / 0.00 ms (average mu = 0.164, current mu = 0.148) allocation failure;
node-red-empty500-1 | [7:0xffffa0950000] 34420 ms: Mark-Compact (reduce) 4048.0 (4112.9) -> 4048.0 (4051.2) MB, pooled: 0 MB, 1686.27 / 0.00 ms (+ 20.1 ms in 6 steps since start of marking, biggest step 5.0 ms, walltime since start of marking 1710 ms) (average mu = 0.118,
node-red-empty500-1 | FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
node-red-empty500-1 | ----- Native stack trace -----
node-red-empty500-1 |

```

Which that leaves my flow like this:

 ![Screenshot 2026-09-03 at 11.28.59](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/2/22c64a8e7cd27d5c425e72468a988e2a537a3229.png)

Thanks to exploring this, I actually fixed my code by removing the endless loop 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [2 November 2026 08:43 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/100 "2026-11-02T08:43:14Z")

</div>

Closed on 2 November 2026 08:43 UTC

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.

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