# Nodejs and npm upgrade issue in the opcua package

**URL:** <https://discourse.nodered.org/t/nodejs-and-npm-upgrade-issue-in-the-opcua-package/60127>\
**Category:** General\
**Created:** [21 March 2022 05:57 UTC](https://discourse.nodered.org/t/nodejs-and-npm-upgrade-issue-in-the-opcua-package/60127 "2022-03-21T05:57:44Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![muharremsari](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/muharremsari/32/7996_2.png) [@muharremsari](https://discourse.nodered.org/u/muharremsari)\
**Post date:** [21 March 2022 05:57 UTC](https://discourse.nodered.org/t/nodejs-and-npm-upgrade-issue-in-the-opcua-package/60127/1 "2022-03-21T05:57:45Z")

</div>

Previously i was sending over someone data with the OPCUA-IIoT-Flex-Server contained in the node-red-contrib-lativ content package

> **[node-red-contrib-lativ](https://flows.nodered.org/node/node-red-contrib-lativ)**
>
> Old IoT/IIoT OPC UA toolbox package for Node-RED based on node-opcua.

I couldn't install this package after update

I get errors shown below

incompatible with your node/npm version: node-red-contrib-lativ@1.0.3

ERR! notsup Actual: {"npm":"8.5.0","node":"v16.14.2"}

How do i resolve this problem

last state of used intallation

Node-red = v2.2.2  
nodejs = v17.7.1  
npm = 6.14.16

Best regards

---

<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:** [21 March 2022 06:17 UTC](https://discourse.nodered.org/t/nodejs-and-npm-upgrade-issue-in-the-opcua-package/60127/2 "2022-03-21T06:17:06Z")

</div>

Drop your nodesjs version back to node16

---

<div class="post-metadata">

**Author:** ![muharremsari](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/muharremsari/32/7996_2.png) [@muharremsari](https://discourse.nodered.org/u/muharremsari)\
**Post date:** [21 March 2022 07:03 UTC](https://discourse.nodered.org/t/nodejs-and-npm-upgrade-issue-in-the-opcua-package/60127/3 "2022-03-21T07:03:57Z")

</div>

I was try this command.

```auto
#sudo npm install -g n

#sudo n 16.14.2

```

---

<div class="post-metadata">

**Author:** ![muharremsari](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/muharremsari/32/7996_2.png) [@muharremsari](https://discourse.nodered.org/u/muharremsari)\
**Post date:** [21 March 2022 07:04 UTC](https://discourse.nodered.org/t/nodejs-and-npm-upgrade-issue-in-the-opcua-package/60127/4 "2022-03-21T07:04:46Z")

</div>

Resul is same:(

> Blockquote

ERR! code EBADENGINE  
2022-03-21T06:55:28.684Z [err] npm ERR! engine Unsupported engine  
2022-03-21T06:55:28.684Z [err] npm ERR! engine Not compatible with your version of node/npm: node-red-contrib-lativ@1.0.3  
2022-03-21T06:55:28.684Z [err] npm ERR! notsup Not compatible with your version of node/npm: node-red-contrib-lativ@1.0.3  
2022-03-21T06:55:28.684Z [err] npm ERR! notsup Required: {"node":"8.x || 10.x"}  
2022-03-21T06:55:28.684Z [err] npm ERR! notsup Actual: {"npm":"8.5.0","node":"v16.14.2"}

> Blockquote

---

<div class="post-metadata">

**Author:** ![muharremsari](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/muharremsari/32/7996_2.png) [@muharremsari](https://discourse.nodered.org/u/muharremsari)\
**Post date:** [21 March 2022 07:09 UTC](https://discourse.nodered.org/t/nodejs-and-npm-upgrade-issue-in-the-opcua-package/60127/5 "2022-03-21T07:09:45Z")

</div>

I review supported node version

Requried node version 8.x || 10.x not compatible with 2.2.2

[https://nodered.org/docs/faq/node-versions](https://nodered.org/docs/faq/node-versions)

---

<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:** [21 March 2022 07:10 UTC](https://discourse.nodered.org/t/nodejs-and-npm-upgrade-issue-in-the-opcua-package/60127/6 "2022-03-21T07:10:45Z")

</div>

Oh crikey. I see from that error it is wanting node 8 or 10. They are both well out of support so really you need to contact the owner of that node to see if they will update it. If not then I’d suggest not using it rather than going back to node 10.

There are other Opcua nodes available

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [21 March 2022 08:18 UTC](https://discourse.nodered.org/t/nodejs-and-npm-upgrade-issue-in-the-opcua-package/60127/7 "2022-03-21T08:18:48Z")

</div>

> [@dceejay](#):
>
> so really you need to contact the owner of that node to see if they will update it.

Unfortunately, this package has no repo on github and its github link points to `biancode/node-red-contrib-iiot-opcua`

biancode took down "`biancode/node-red-contrib-iiot-opcua`" package sometime back (cant remember reason why now but it is now gone)

---

<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:** [20 May 2022 08:19 UTC](https://discourse.nodered.org/t/nodejs-and-npm-upgrade-issue-in-the-opcua-package/60127/8 "2022-05-20T08:19:26Z")

</div>

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