Not compatible with your version of node/npm

[mhechthz]

I just wanted to update my node-red-contrib-opcua in my docker node-red. I wanted to go to from my vewrsion 0.2.84 the newest available version 0.2.307. Installation failed and the old opcua node was also no longer available.

So I wanted to go back to my old version 0.2.84. Installation again failes:

bash-5.0$ npm install --no-audit --no-update-notifier --no-fund --save --save-prefix="~" --production [email protected]
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">=12.0.0"} (current: {"node":"10.22.0","npm":"6.14.6"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">= 12.4.0"} (current: {"node":"10.22.0","npm":"6.14.6"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">=12"} (current: {"node":"10.22.0","npm":"6.14.6"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">=12"} (current: {"node":"10.22.0","npm":"6.14.6"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">=12"} (current: {"node":"10.22.0","npm":"6.14.6"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]

+ [email protected]
updated 1 package in 53.351s

I'm inside docker and didn't change anything on the container since last update.

I recently updated the ubuntu system where the docker container runs on but this shouldn't affect the container.

Node-Red is v1.1.3

[mikakaraila]

Hard life, I expect nodejs v12 is not anymore maintained. LTS versions are v16, v18 and newer are still maintained.

Node-red itself is also out-of-date and not maintained anymore.

AND node-opcua itself needs at least nodejs v14 or v16!

[mhechthz]

Hi, I just set up a new Docker container with node-red 2.2.3

OPC-UA 0.2.307 can now be installed but I get following error on start:

14 Jun 09:59:59 - [warn] [node-red-contrib-opcua/OpcUa-Client] Error [ERR_UNKNOWN_BUILTIN_MODULE]: No such built-in module: node:stream/promises

Node.js is now v14.18.

[mhechthz]

I followed the instructions in https://github.com/mikakaraila/node-red-contrib-opcua/issues/537 but now I run into other problems with node.js 16.x

So I would need a version that works with node.js 14.x

[mikakaraila]

Ask from @erossignon I expect it is not supported.... node-opcua-file-transfer uses stream/promises. It is not existing in v14.

[mikakaraila]

Just comment file-transfer require lines and do not use file-transfer then code "should" work.

[federicoabait]

Hi @mikakaraila

I have tried to install the latest version of node node-red-contrib-opcua 0.2.308, in a version of node-red v2.1.1 (within a docker container) and I get the following error

2023-06-30T09:52:20.295Z [err] notsup 2023-06-30T09:52:20.295Z [err] Unsupported engine for [email protected]: wanted: {"node":">=15"} (current: {"node":"14.18.1","npm":"6.14.15"}) 2023-06-30T09:52:20.295Z [err] npm 2023-06-30T09:52:20.295Z [err]
2023-06-30T09:52:20.296Z [err] ERR! 2023-06-30T09:52:20.296Z [err]
2023-06-30T09:52:20.296Z [err] notsup 2023-06-30T09:52:20.296Z [err] Not compatible with your version of node/npm: [email protected]

Can you help me? Thanks Regards

[mikakaraila]

As error message "says": Required version is 15 or newer and you have v14

On Fri, Jun 30, 2023, 12:53 federicoabait @.***> wrote:

Hi @mikakaraila https://github.com/mikakaraila

I have tried to install the latest version of node node-red-contrib-opcua 0.2.308, in a version of node-red v2.1.1 (within a docker container) and I get the following error

2023-06-30T09:52:20.295Z [err] notsup 2023-06-30T09:52:20.295Z [err] Unsupported engine for @.: wanted: {"node":">=15"} (current: {"node":"14.18.1","npm":"6.14.15"}) 2023-06-30T09:52:20.295Z [err] npm 2023-06-30T09:52:20.295Z [err] 2023-06-30T09:52:20.296Z [err] ERR! 2023-06-30T09:52:20.296Z [err] 2023-06-30T09:52:20.296Z [err] notsup 2023-06-30T09:52:20.296Z [err] Not compatible with your version of node/npm: @.

Can you help me? Thanks Regards

— Reply to this email directly, view it on GitHub https://github.com/mikakaraila/node-red-contrib-opcua/issues/568#issuecomment-1614419715, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABHRYDFYWEZAV5BO4WXU5ZTXN2O2JANCNFSM6AAAAAAZF5XOJI . You are receiving this because you were mentioned.Message ID: @.***>

[federicoabait]

Yes, but unfortunately I can't change the version. There is some work around. Or is it possible to use a node-red-contrib-opque version compatible with node 1.4? thanks

[mikakaraila]

It is actually limited by node-opcua. So there's no other solution than use older version.

On Fri, Jun 30, 2023, 13:52 federicoabait @.***> wrote:

Yes, but unfortunately I can't change the version. There is some work around. Or is it possible to use a node-red-contrib-opque version compatible with node 1.4? thanks

— Reply to this email directly, view it on GitHub https://github.com/mikakaraila/node-red-contrib-opcua/issues/568#issuecomment-1614483619, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABHRYDE4NPSUE5DXW4TOQALXN2VVRANCNFSM6AAAAAAZF5XOJI . You are receiving this because you were mentioned.Message ID: @.***>