# Node-RED install on Raspbian Buster Lite

**URL:** <https://discourse.nodered.org/t/node-red-install-on-raspbian-buster-lite/13106>\
**Category:** General\
**Created:** [10 July 2019 12:51 UTC](https://discourse.nodered.org/t/node-red-install-on-raspbian-buster-lite/13106 "2019-07-10T12:51:43Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![johnwalicki](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/johnwalicki/32/8848_2.png) [@johnwalicki](https://discourse.nodered.org/u/johnwalicki)\
**Post date:** [10 July 2019 12:51 UTC](https://discourse.nodered.org/t/node-red-install-on-raspbian-buster-lite/13106/1 "2019-07-10T12:51:43Z")

</div>

I just burned a Raspbian Buster Lite image and want to install Node-RED. The new Node-RED [documentation](https://nodered.org/docs/getting-started/raspberrypi) suggests running this command:

```auto
$ bash <(curl -sL https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered)

```

It fails however. The last line of **/var/log/nodered-install.log** reports:  
`sudo: npm: command not found`

Higher up in the log, during the fresh install of Node LTS, it says

```auto
The following additional packages will be installed:
  libc-ares2 libnode64 libuv1 nodejs-doc
Suggested packages:
  npm

```

I fixed the error by downloading the script and explicitly installing npm when installing Node LTS

---

<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:** [10 July 2019 13:00 UTC](https://discourse.nodered.org/t/node-red-install-on-raspbian-buster-lite/13106/2 "2019-07-10T13:00:07Z")

</div>

What exactly did you add to the script?

Npm is included in the node package from nodesource. You should not have needed to do anything.

---

<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:** [10 July 2019 14:05 UTC](https://discourse.nodered.org/t/node-red-install-on-raspbian-buster-lite/13106/4 "2019-07-10T14:05:32Z")

</div>

Ah actually the error is just before that - caused by debian moving from testing to stable - and then not being happy to just upgrade things... fix pushed to script - should be ok to re-run.

---

<div class="post-metadata">

**Author:** ![johnwalicki](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/johnwalicki/32/8848_2.png) [@johnwalicki](https://discourse.nodered.org/u/johnwalicki)\
**Post date:** [10 July 2019 14:08 UTC](https://discourse.nodered.org/t/node-red-install-on-raspbian-buster-lite/13106/5 "2019-07-10T14:08:36Z")

</div>

Once I additionally installed the npm package via apt-get, the script ran to completion.  
$ node -v  
v10.15.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:** [10 July 2019 14:10 UTC](https://discourse.nodered.org/t/node-red-install-on-raspbian-buster-lite/13106/6 "2019-07-10T14:10:26Z")

</div>

yes - running it a second time would have the effect of then doing the update and upgrade over the top... but shouldn't have been necessary.

---

<div class="post-metadata">

**Author:** ![johnwalicki](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/johnwalicki/32/8848_2.png) [@johnwalicki](https://discourse.nodered.org/u/johnwalicki)\
**Post date:** [10 July 2019 14:28 UTC](https://discourse.nodered.org/t/node-red-install-on-raspbian-buster-lite/13106/7 "2019-07-10T14:28:28Z")

</div>

Dave - The fixed script ran successfully. Thanks.  
Nick - I just added npm to the appropriate install step (I know it should not have been necessary, but it was)  
`if sudo apt-get install -y nodejs npm curl`  
Dave's fix was a better approach on Raspbian Buster as it moved from testing to stable.  
-- John

---

<div class="post-metadata">

**Author:** ![okbayou](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/okbayou/32/15299_2.png) [@okbayou](https://discourse.nodered.org/u/okbayou)\
**Post date:** [10 July 2019 20:24 UTC](https://discourse.nodered.org/t/node-red-install-on-raspbian-buster-lite/13106/8 "2019-07-10T20:24:43Z")

</div>

I had similar errors: sudo: npm: command not found  
and got hung up on the step where the script tries to install nodejs and finally I saw on the Raspberry forum to run: **sudo apt update --allow-releaseinfo-change**  
This fixed the problem and the installation ran OK after that.

---

<div class="post-metadata">

**Author:** ![johnwalicki](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/johnwalicki/32/8848_2.png) [@johnwalicki](https://discourse.nodered.org/u/johnwalicki)\
**Post date:** [10 July 2019 20:41 UTC](https://discourse.nodered.org/t/node-red-install-on-raspbian-buster-lite/13106/9 "2019-07-10T20:41:15Z")

</div>

Yup - The **--allow-releaseinfo-change** flag was the fix that Dave implemented in the install script. Works for me now.  
-- John