Hi there,
I can’t seem to install [email protected] node into a Node Red v3.0.2 environmet. I’ve read of similar issues with other users and picked up several workarounds, with none of them fixing the issue… 
I’m running a Node Red v3.0.2 ARMV7 image on Docker:
‘4 Dec 12:45:13 - [info] Node-RED version: v3.0.2
4 Dec 12:45:13 - [info] Node.js version: v16.16.0
4 Dec 12:45:13 - [info] Linux 5.10.109-ti-r45 arm LE’
I’ve tried all the “tricks”:
-executing the image bash as root
-updateing to a newer version of npm, now running 8.11.0
-setting timeout to 9999999 and omitting all optionals (‘npm install --timeout=9999999 --omit=optional [email protected]’)
-increasing fetch timeout and retry variables:
-‘npm config set fetch-retries=10’
-‘npm config set fetch-retry-factor=20’
-‘npm config set fetch-timeout=9999999’
-‘npm config set fetch-retry-maxtimeout=9999999’
-define the noproxy variable:
-‘npm config set noproxy=“registry.npmjs.org”’
-deleting all the hidden directories (starting with “.” in ‘/usr/src/node-red/node-modules/’)
I believe the installation procedure is almost finished, until it runs into Socket timeout error:
‘npm ERR! code ERR_SOCKET_TIMEOUT
npm ERR! network Socket timeout
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network ‘proxy’ config is set properly. See: ‘npm help config’
npm ERR! A complete log of this run can be found in:
npm ERR! /data/.npm/_logs/2022-12-04T11_39_53_037Z-debug-0.log’
Have I missed something or is there a bug or incompatibility somewhere? Is there any workaround?
Below extract from the log:
‘…
519 silly tarball no local data for browser-sync@https://registry.npmjs.org/browser-sync/-/browser-sync-2.27.10.tgz. Extracting by manifest.
520 timing metavuln:cache:get:security-advisory:moment-timezone:xgIIK9a6p++H2BBkK/X/yh1VIeLSVriaB+EiZd95y+zPdQ2yRsQLM4mVWFCRE0JMsujeHAXeIS0LNKSc71DlYw== Completed in 8686ms
521 timing metavuln:cache:get:security-advisory:moment-timezone:1Kv0o2LTVcP3BPzSjgyG34QAmxaGQGBeuKzGDrllGX9StWpvs/x1ed3JjiGcfIccIeG5V2SS5XlISxA55ymv4A== Completed in 8599ms
522 timing reifyNode:node_modules/browser-sync/node_modules/finalhandler Completed in 133520ms
523 timing reifyNode:node_modules/browser-sync/node_modules/cookie Completed in 175404ms
524 verbose stack Error: Socket timeout
524 verbose stack at TLSSocket.onTimeout (/usr/local/lib/node_modules/npm/node_modules/agentkeepalive/lib/agent.js:346:23)
524 verbose stack at TLSSocket.emit (node:events:539:35)
524 verbose stack at TLSSocket.Socket._onTimeout (node:net:516:8)
524 verbose stack at listOnTimeout (node:internal/timers:559:17)
524 verbose stack at processTimers (node:internal/timers:502:7)
525 verbose cwd /usr/src/node-red/node_modules
526 verbose Linux 5.10.109-ti-r45
527 verbose node v16.16.0
528 verbose npm v8.11.0
529 error code ERR_SOCKET_TIMEOUT
530 error network Socket timeout
531 error network This is a problem related to network connectivity.
531 error network In most cases you are behind a proxy or have bad network settings.
531 error network
531 error network If you are behind a proxy, please make sure that the
531 error network ‘proxy’ config is set properly. See: ‘npm help config’
532 verbose exit 1
533 timing npm Completed in 381423ms
534 verbose unfinished npm timer command:install 1670153995872
535 verbose unfinished npm timer reify 1670153995941
536 verbose unfinished npm timer reify:audit 1670154190959
537 verbose unfinished npm timer reify:unpack 1670154191746
538 verbose unfinished npm timer reifyNode:node_modules/stream-throttle 1670154191759
539 verbose unfinished npm timer reifyNode:node_modules/slugify 1670154191778
540 verbose unfinished npm timer reifyNode:node_modules/multicast-dns 1670154191809
541 verbose unfinished npm timer reifyNode:node_modules/dev-ip 1670154191836
…’
Thanks!
Stefan