# Node js version

**URL:** <https://discourse.nodered.org/t/node-js-version/64434>\
**Category:** General\
**Created:** [27 June 2022 19:55 UTC](https://discourse.nodered.org/t/node-js-version/64434 "2022-06-27T19:55:13Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [27 June 2022 19:55 UTC](https://discourse.nodered.org/t/node-js-version/64434/1 "2022-06-27T19:55:13Z")

</div>

Updated one pi 4 to the latest node js and to my horror it says I'm at ver 17.1. Other than breaking one node it seems to run. Should I panic and run in tight little circles or should I be relatively OK as it seems node red wants 16x.  
[EDIT] V17.9.0

---

<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:** [27 June 2022 20:25 UTC](https://discourse.nodered.org/t/node-js-version/64434/2 "2022-06-27T20:25:24Z")

</div>

TBH, I'd switch to 16 LTS or 18 current.

PS, if you had use the official installer script, you can simply specify `--node16` and it installs everything for you (node-red, the service and node-js/npm)

---

<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:** [27 June 2022 20:26 UTC](https://discourse.nodered.org/t/node-js-version/64434/3 "2022-06-27T20:26:12Z")

</div>

Don't panic certainly. But best to fix it now. When upgrading Node.js, you want the latest LTS version and not the very latest. LTS versions will normally have even numbers. Easy enough to change.

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [27 June 2022 23:20 UTC](https://discourse.nodered.org/t/node-js-version/64434/4 "2022-06-27T23:20:27Z")

</div>

So I did roll back to v16x, I originally used the install script but as I upgraded over time I had not updated node js so I found myself at 2.2.2 running node 12. When I ran the node update I asked for latest, my mistake, instead of LTS current. Did a rollback and the one misbehaving node did straighten out. Lesson learned

---

<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:** [28 June 2022 06:43 UTC](https://discourse.nodered.org/t/node-js-version/64434/5 "2022-06-28T06:43:10Z")

</div>

It would be helpful to know what node didn't work - it will need fixing eventually.

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [28 June 2022 13:20 UTC](https://discourse.nodered.org/t/node-js-version/64434/6 "2022-06-28T13:20:33Z")

</div>

It was an obscure node to run a bme280 that hasn't been updated for 3 years. I don't think it's worth your time to look at and I'm going to ditch it in favor of a different sensor and a supported node.

---

<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:** [27 August 2022 13:21 UTC](https://discourse.nodered.org/t/node-js-version/64434/7 "2022-08-27T13:21:07Z")

</div>

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