Node-red-contrib-google-cloud install issue

Support
1

While installing node-red-contrib-google-cloud. Any help is appreciated

2023-08-11T16:48:12.135Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-google-cloud@0.0.26

2023-08-11T16:48:17.227Z [err] npm

2023-08-11T16:48:17.227Z [err] WARN config production Use --omit=dev instead.

2

You are going to need to supply some more context here, because just that log on it’s own doesn’t tell us anything.

  • Are there more lines after that?
  • Was there any messages in the Node-RED editor?
  • How long between you clicking on the install button until there was any message/warning?

Also is this running in FlowForge Cloud or on your own hardware?

If on FlowForge Cloud what instance size are you running on?

3

No additional output from pallet in the dashboard.
Below is from flow forge node red logs
Testing out cloud.
Small instance.

8/11/2023 12:48:12 PM

[info]

Installing module: node-red-contrib-google-cloud, version: 0.0.26

8/11/2023 12:49:33 PM

[warn]

Installation of module node-red-contrib-google-cloud failed:

8/11/2023 12:49:33 PM

[warn]

8/11/2023 12:49:33 PM

[warn]

npm WARN config production Use --omit=dev instead.

8/11/2023 12:49:33 PM

[warn]

8/11/2023 12:49:33 PM

Error: Install failed

8/11/2023 12:49:33 PM

at /usr/src/node-red/node_modules/@node-red/registry/lib/installer.js:285:25

8/11/2023 12:49:33 PM

at runMicrotasks ()

8/11/2023 12:49:33 PM

at processTicksAndRejections (node:internal/process/task_queues:96:5)

8/11/2023 12:49:33 PM

[error]

{“status”:400}

4

This installs fine on my local node red install.

5

OK, that node pulls in a lot of dependencies which means that npm will end up using a lot of memory, potentially more than the amount assigned to your instance which means it will get killed by the hosting system.

A quick fix will be to suspend the instance and then restart it. As the instance starts up it should install the node before starting Node-RED and hence not hitting the limit. The node should have been added to the list of used nodes, but if not you can add it in the instance settings.

The other option is to move to the larger instance types, but that will incur a cost as only a single small instance is included in the free trial.

6

I think you are right. Oddly when restarting I get different behavior from completely stopping and starting.
Restarting it would never start. Stopping and starting caused a boot loop. I will remove this palette and do this test locally.