# Issue installing Node-RED with Homebridge

**URL:** <https://discourse.nodered.org/t/issue-installing-node-red-with-homebridge/31259>\
**Category:** General\
**Created:** [6 August 2020 22:11 UTC](https://discourse.nodered.org/t/issue-installing-node-red-with-homebridge/31259 "2020-08-06T22:11:25Z")\
**Posts on this page:** 5\
**Page:** 2

<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:** [7 August 2020 10:36 UTC](https://discourse.nodered.org/t/issue-installing-node-red-with-homebridge/31259/21 "2020-08-07T10:36:06Z")

</div>

we only touch node.js if it's not v8, 10, 12 or 14... if it is there already we don't touch it so as long as they are using a sensible version it should be ok... (should.... 🙂

---

<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:** [7 August 2020 10:39 UTC](https://discourse.nodered.org/t/issue-installing-node-red-with-homebridge/31259/22 "2020-08-07T10:39:15Z")

</div>

Just to point out, the issues yesterday were specific to trying to install scoped modules - so `registry.npmjs.org` was available and it was able to start installing the `node-red` module, but it just fell down when it got to the `@node-red/util` scoped module dependency.

So whilst a check for the general availability of the registry is good to have it would not have saved this situation.

---

<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:** [7 August 2020 10:44 UTC](https://discourse.nodered.org/t/issue-installing-node-red-with-homebridge/31259/23 "2020-08-07T10:44:04Z")

</div>

oh joy... would picking one specifically help (until we rename it) ?

maybe curl -I [https://registry.npmjs.org/@node-red/util](https://registry.npmjs.org/@node-red/util)

---

<div class="post-metadata">

**Author:** ![ristomatti](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ristomatti/32/5857_2.png) [@ristomatti](https://discourse.nodered.org/u/ristomatti)\
**Post date:** [7 August 2020 11:01 UTC](https://discourse.nodered.org/t/issue-installing-node-red-with-homebridge/31259/24 "2020-08-07T11:01:10Z")

</div>

I skimmed through the install script and noted there are steps to `npm remove` NR but also to `rm -rf` it from the global `node_modules` dir. I assume you've found it necessary to do that instead of just doing an `npm install` on top of the old install and let `npm` do the cleanup?

I'm wondering if skipping the uninstall step could have prevented the old version from being removed in this case or would it have anyway failed...

---

<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:** [6 October 2020 11:01 UTC](https://discourse.nodered.org/t/issue-installing-node-red-with-homebridge/31259/25 "2020-10-06T11:01:26Z")

</div>

Closed on 6 October 2020 11:01 UTC

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

[Previous page](https://discourse.nodered.org/t/issue-installing-node-red-with-homebridge/31259.md?page=1)