# Updating Node-RED on IBM Cloud

**URL:** <https://discourse.nodered.org/t/updating-node-red-on-ibm-cloud/9671>\
**Category:** General\
**Created:** [2 April 2019 01:37 UTC](https://discourse.nodered.org/t/updating-node-red-on-ibm-cloud/9671 "2019-04-02T01:37:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mascapollo](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mascapollo/32/24160_2.png) [@mascapollo](https://discourse.nodered.org/u/mascapollo)\
**Post date:** [2 April 2019 01:37 UTC](https://discourse.nodered.org/t/updating-node-red-on-ibm-cloud/9671/1 "2019-04-02T01:37:11Z")

</div>

I upgraded node red to 0.20.3 on IBM Cloud using the instructions in this link:

[https://nodered.org/docs/platforms/bluemix](https://nodered.org/docs/platforms/bluemix)

Then I got an error saying that for node-red-node-email 1.3.0 needs node.js version \>=8. So I edited the package.jason engines:

"engines": {  
"node": "8.x"  
}

and restaged the application. The restaging log shows that it is installing node.js v8.15.1:

-----\> Installing binaries  
engines.node (package.json): 8.x  
engines.npm (package.json): unspecified (use default)

```
      Resolving node version 8.x via 'node-version-resolver'
      Downloading and installing node 8.15.1...
      Using default npm version: 6.4.1

```

But I stiil get the error for the email node saying it needs node.js version \>=8

Any help appreciated.

Regards

Miguel Suarez

---

<div class="post-metadata">

**Author:** ![donovat](https://avatars.discourse-cdn.com/v4/letter/d/ad7895/32.png) [@donovat](https://discourse.nodered.org/u/donovat)\
**Post date:** [20 August 2019 07:52 UTC](https://discourse.nodered.org/t/updating-node-red-on-ibm-cloud/9671/2 "2019-08-20T07:52:37Z")

</div>

Hi Miguel, I had the same issue after upgrading NodeRed. I got around the issue by adding the sendmail node directly into my package.json file as a depandancy. I am still not 100% sure why the node dependancy did not confirm that NodeRed was now running with Node =\>8. It would be my guess that one of the hidden cache files contains old info, and was not being updated by the cloud deployment. I had a similar issue with the Serail Port Node, which still believed it was part of the old basic NodeRed nodes.