# Upgrade Node-RED from Node.js 16.20.2 to 18.x or 20.x

**URL:** <https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224>\
**Category:** Développement\
**Created:** [December 6, 2024, 4:44pm UTC](https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224 "2024-12-06T16:44:55Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [February 14, 2025, 10:04am UTC](https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224/2 "2025-02-14T10:04:44Z")

</div>

Hi @prohand,

I’m bringing this topic up again, because indeed it would be good to update.

The problem is that this update is, in my opinion, a breaking change.

If we force all instances to update Node-RED, it could break installations, right? And that, I think, we really don’t want 😬

Wouldn’t the solution be to add a Node-RED version selector in the interface of this integration?

---

_[View the full topic](https://community.gladysassistant.com/t/upgrade-node-red-avec-nodejs-16-20-2-to-18-x-ou-20-x/9224)._