# 🎉 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:** 4

<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:** [19 June 2026 10:56 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/67 "2026-06-19T10:56:55Z")

</div>

> <https://github.com/node-red/node-red/pull/5836>
>
> \## Types of changes
> 
> \- \[x\] Bugfix (non-breaking change which fixes an issue)
> …- \[\] New feature (non-breaking change which adds functionality)
> 
> \## Proposed changes
> 
> Request from: https://discourse.nodered.org/t/node-red-5-now-available/101239/64
> 
> Add a button to ignore the import of unknown types.
> 
> Allow to import a flow without having to install the missing modules.
> 
> Preview:
> 
> \<img width="512" height="203" alt="Capture d’écran 2026-06-19 à 12 54 51" src="https://github.com/user-attachments/assets/190b3aa1-2836-4261-8dec-ae99375496db" /\>
> 
> 
> \## Checklist
> 
> \- \[x\] I have read the \[contribution guidelines\](https://github.com/node-red/node-red/blob/main/CONTRIBUTING.md)
> \- \[\] For non-bugfix PRs, I have discussed this change on the forum/slack team.
> \- \[x\] I have run \`npm run test\` to verify the unit tests pass
> \- \[\] I have added suitable unit tests to cover the new/changed functionality

---

<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:** [19 June 2026 11:14 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/68 "2026-06-19T11:14:49Z")

</div>

> [@jbudd](#):
>
> It is a little annoying there is no Cancel button

Are you wanting to cancel the import or ignore the install of missing nodes?

---

<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:** [19 June 2026 11:16 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/69 "2026-06-19T11:16:51Z")

</div>

Good question.

Generally _I_ would want to cancel the import but the other is an equally valid choice.

---

<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:** [19 June 2026 11:28 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/70 "2026-06-19T11:28:12Z")

</div>

A slight gap between highlighted node and the blue line does look better than the v4 highlight.

If you inject to a node which is already highlighted, the blue surround is not immediately expanded  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/7/17f38d69b43e44fce1f0ac61ef41edd1c3e5d451.png)

The line crowds the status message slightly.

The blue line does disappear behind the input and output connectors. Maybe it should be behind the status message too?

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

---

<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:** [19 June 2026 13:26 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/71 "2026-06-19T13:26:36Z")

</div>

> [@jbudd](#):
>
> If you inject to a node which is already highlighted, the blue surround is not immediately expanded

I thought that was handled... it was something I definitely remember working on.. will take a look.

---

<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:** [19 June 2026 13:31 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/72 "2026-06-19T13:31:32Z")

</div>

I'm looking at v5.0.0 beta 6

---

<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:** [19 June 2026 13:43 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/73 "2026-06-19T13:43:37Z")

</div>

Best to install the released version.

---

<div class="post-metadata">

**Author:** ![Buckskin](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@Buckskin](https://discourse.nodered.org/u/Buckskin)\
**Post date:** [19 June 2026 14:57 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/74 "2026-06-19T14:57:21Z")

</div>

Just chucking in my unasked for 2 penny worth, I like the blue highlight like it is.

---

<div class="post-metadata">

**Author:** ![RafaelMuynarsk](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rafaelmuynarsk/32/26492_2.png) [@RafaelMuynarsk](https://discourse.nodered.org/u/RafaelMuynarsk)\
**Post date:** [19 June 2026 17:53 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/75 "2026-06-19T17:53:49Z")

</div>

That's a good point. And with longer status messages, they end up overlapping that area anyway, so you still get the text quite close to the blue line.

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/4/74a2cb3eb6e63ca984c0cb7053a130e4972c0619.png)

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

---

<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:** [20 June 2026 06:13 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/76 "2026-06-20T06:13:20Z")

</div>

Split this topic on 20 June 2026 06:13 UTC

A post was split to a new topic: [Language in the code editor context menu is incorrect](https://discourse.nodered.org/t/language-in-the-code-editor-context-menu-is-incorrect/101324)

---

<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:** [20 June 2026 07:57 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/77 "2026-06-20T07:57:00Z")

</div>

![Screenshot 2026-06-20 at 09.54.04](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/0/60fdd96b4a642a699579c2c6d9eafdc67319b73c.png)

I guess that's about the only REAL fix possible 😉 /s

But honestly, I'd take adding a long name as a fix since I don't really know what the "cron-plus" node is triggering. Perhaps a better title would be "trigger every X minutes to update Y" ... same with the mqtt producer.

My answer is only half in jest!

---

<div class="post-metadata">

**Author:** ![algaillard](https://avatars.discourse-cdn.com/v4/letter/a/c5a1d2/32.png) [@algaillard](https://discourse.nodered.org/u/algaillard)\
**Post date:** [21 June 2026 09:57 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/78 "2026-06-21T09:57:23Z")

</div>

I have this version newly installed on Home Assistant.  
It seems that Homekit Bridge and AppleTV nodes cannot be installed,  
-----------------------------------------------------------

2026-06-21T10:02:01.769Z Installer : node-red-contrib-homekit-bridged 1.7.3  
2026-06-21T10:02:01.868Z /usr/bin/node /opt/node\_modules/npm/bin/npm-cli.js install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --omit=dev --engine-strict -- node-red-contrib-homekit-bridged@1.7.3  
2026-06-21T10:02:09.577Z [err] npm error code EBADENGINE  
2026-06-21T10:02:09.577Z [err] npm error engine Unsupported engine  
2026-06-21T10:02:09.579Z [err] npm error engine Not compatible with your version of node/npm: hap-nodejs@0.12.3  
2026-06-21T10:02:09.583Z [err] npm error notsup Not compatible with your version of node/npm: hap-nodejs@0.12.3  
2026-06-21T10:02:09.583Z [err] npm error notsup Required: {"node":"^18 || ^20 || ^22"}  
2026-06-21T10:02:09.583Z [err] npm error notsup Actual: {"node":"v24.16.0","npm":"11.16.0"}  
2026-06-21T10:02:09.595Z [err] npm error A complete log of this run can be found in: /root/.npm/\_logs/2026-06-21T10\_02\_02\_325Z-debug-0.log  
2026-06-21T10:02:09.781Z rc=1

I run another instance on a Mac and there is no problem.  
Is it due to this update ?

---

<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:** [21 June 2026 10:04 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/79 "2026-06-21T10:04:53Z")

</div>

This is an issue with the node, not with Node-RED. Please contact the author(s).

---

<div class="post-metadata">

**Author:** ![algaillard](https://avatars.discourse-cdn.com/v4/letter/a/c5a1d2/32.png) [@algaillard](https://discourse.nodered.org/u/algaillard)\
**Post date:** [21 June 2026 10:19 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/81 "2026-06-21T10:19:20Z")

</div>

Thanks, I'll try to update in HA terminal. I thought that all necessary packages were installed when using the HA Node-Red integration

---

<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:** [21 June 2026 10:42 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/82 "2026-06-21T10:42:25Z")

</div>

> [@algaillard](#):
>
> I thought that all necessary packages were installed when using the HA Node-Red integration

Did that install nodejs 24? For node-red-contrib-homekit-bridged you need to stick to 22, until the node is modified to use the latest version of hap-nodejs.

---

<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:** [21 June 2026 11:17 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/83 "2026-06-21T11:17:28Z")

</div>

v2 of that node is currently under development. This new version will support NodeJS v24. You just need to wait a little longer or install the beta version of v2 or an older version of NodeJS.

---

<div class="post-metadata">

**Author:** ![algaillard](https://avatars.discourse-cdn.com/v4/letter/a/c5a1d2/32.png) [@algaillard](https://discourse.nodered.org/u/algaillard)\
**Post date:** [21 June 2026 13:22 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/84 "2026-06-21T13:22:22Z")

</div>

Thanks, I think I’ll wait for this node to be updated and use my old instance in the meantime

---

<div class="post-metadata">

**Author:** ![algaillard](https://avatars.discourse-cdn.com/v4/letter/a/c5a1d2/32.png) [@algaillard](https://discourse.nodered.org/u/algaillard)\
**Post date:** [21 June 2026 13:23 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/85 "2026-06-21T13:23:14Z")

</div>

> [@GogoVega](#):
>
> v2 of that node is currently under development. This new version will support NodeJS v24. You just need to wait a little longer or install the beta version of v2 or an older version of NodeJS.

Thanks I'll wait

---

<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:** [23 July 2026 05:30 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/86 "2026-07-23T05:30:20Z")

</div>

I can still not wrap my head around the panel behaviour, when i drag a panel, I lose the debug panel and it decides to show another panel instead.

Is this just me ? The behaviour is not natural from a user experience.  
Can someone explain in simple terms how this exactly works ?

---

<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:48 UTC](https://discourse.nodered.org/t/node-red-5-now-available/101239/87 "2026-07-23T08:48:28Z")

</div>

Do you mean this:

![Screen Recording 2026-07-23 at 10.43.00-3](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/e/e/ee871a3882ab43074f0293588f8839790db07667.gif)

Which can be used to adjust the location of the debug panel, either top or bottom on the left (or if dragged to the right, top or bottom right side - not shown).

Node-RED 5 basically has four separate side bars with each of them having a choice of different plugins/sidebars that can be shown. The drag shown in the animation is the placement of those the sidebars. It only happens if clicking on the the top bar of the sidebar.

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

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