Installing new nodes manually stuck at idealTree:.node-red: sill idealTree buildDeps

General
1

Hello ,

I want to install https node manually on node red instance that runs locally under debian.

after this command npm install node-red-contrib-https the install seems to be stuck at :

 
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠙ idealTree:.node-red: sill idealTree buildDeps

any idea what is going on here ?

Thanks

2
  1. Did you try installing it via the 'Manage palette' option in the editor?
  2. What version of NR and Node.js are you running? (you can get this from the startup log)
  3. what platform are you running on?
  4. are you using Home Assistant or Docker?

One thing to note is that node has not been updated in almost 2 1.2 years.

3

What hardware are you running on? Building dependencies can take a long time on low power hardware. Give it an hour before you give up.

4
  1. initially from 'manage palette' as it didn't work i tried with npm
  2. NR V3.1.5 , node.js v10.19.0
  3. I'm running on a linux VM in corporate environment
  4. No i'm not using HA , tried from another VM where i have NR running on docker and i got a timeout
npm ERR! code ETIMEOUT
npm ERR! errno ETIMEOUT
npm ERR! request to https://registry.npmjs.org/node-red-contrib-https failed, reason: A "socket" was not created for HTTP request before 300001ms
5

i'm running on a VM with relatively good hardware

6

That is an old version of node.js you should try upgrading it to node.js v20 and do the install again.

7

What happens if, in a command window inside the VM, you run
wget https://registry.npmjs.org/node-red-contrib-https
It should create a file with the definition of the node in it. It should take about a second. If it fails or is slow then you have a network problem.

8

Given the timeout error and the fact that you're using Node.js v10.19.0, upgrading to a more recent version of Node.js, like v20, is essential. Many npm packages, including node-red-contrib-https, might not be fully compatible with older versions. Additionally, try running wget https://registry.npmjs.org/node-red-contrib-https in your VM to see if it's a network issue. If this fails or is slow, there might be network restrictions or proxy settings in your corporate environment that need addressing.

9

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