# So, with NR 1.2.x Node is not a global install?

**URL:** <https://discourse.nodered.org/t/so-with-nr-1-2-x-node-is-not-a-global-install/34683>\
**Category:** General\
**Created:** [22 October 2020 15:39 UTC](https://discourse.nodered.org/t/so-with-nr-1-2-x-node-is-not-a-global-install/34683 "2020-10-22T15:39:14Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Andrei](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/andrei/32/10446_2.png) [@Andrei](https://discourse.nodered.org/u/Andrei)\
**Post date:** [23 October 2020 00:54 UTC](https://discourse.nodered.org/t/so-with-nr-1-2-x-node-is-not-a-global-install/34683/6 "2020-10-23T00:54:41Z")

</div>

> [@Nodi.Rubrum](#):
>
> I find... that the node-red-serialport module was not installed, yet it was clearly qualified in the package.json, under ~/.node-red/ on a new Pi image. So out of 40 odd modules installed, one was not?

Not surprisingly and the likely explanation is here:

> [@Unable to start node-red after upgrade to 1.0.2](https://discourse.nodered.org/t/unable-to-start-node-red-after-upgrade-to-1-0-2/17131/21):
>
> some packages ship with pre-built versions of binaries for the most popular platforms (eg serialport) - so don't need tools - but if there is a combination they don't have (or there is no prebuild) then they have to be built - eg serialport on Armv6 for Pi - so it is entirely possible that this package may have shipped node10 binary but not yet node12 - etc. ( this is the the main long standing reason we recommended the LTS versions of Node.js ). Our windows install docs do talk about how to i…

---

_[View the full topic](https://discourse.nodered.org/t/so-with-nr-1-2-x-node-is-not-a-global-install/34683)._
