# Npm, versioning and palette manager confusions

**URL:** <https://discourse.nodered.org/t/npm-versioning-and-palette-manager-confusions/44064>\
**Category:** General\
**Created:** [12 April 2021 20:15 UTC](https://discourse.nodered.org/t/npm-versioning-and-palette-manager-confusions/44064 "2021-04-12T20:15:26Z")\
**Posts on this page:** 1\
**Showing post:** 52

<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:** [15 April 2021 10:16 UTC](https://discourse.nodered.org/t/npm-versioning-and-palette-manager-confusions/44064/52 "2021-04-15T10:16:42Z")

</div>

The existing script leaves 10 or 12 if they are there (unless it is the apt installed old version of 10 :-)... If there is no node.js at all it will install 12.

So if the node updates have worked you should be on node10 plus latest node-red plus latest versions of all extra nodes... (which indeed as Colin points out may break some - so yeah need to think about that - as I said this is mainly me thinking about Node-RED v2 - so maybe I need a different script so it obviously different etc)

If you want to jump to node 14 then if you are on Pi3 or 4 then (for now) the way is to edit your /etc/apt/sources.list.d/nodesource.list file and change node\_10.x to node\_14.x - then use the use the usual `sudo apt update && sudo apt full-upgrade` to get node14 ... and then finally in the `.node-red` folder - run `npm rebuild`  
If you are on arm6 (Pi0,1,2) then it's a bit more involved as we need to hack the script.

---

_[View the full topic](https://discourse.nodered.org/t/npm-versioning-and-palette-manager-confusions/44064)._