Strange problems when trying to install nodes in Node Red after latest update
Recently, I updated Node Red add on + Node-RED Companion Integration. Now I can’t install any new nodes at all? I do not understand what the problem is from the log?
This is my current setup:
Home Assistant
Core 2024.10.2
Supervisor 2024.10.2
Operating System 13.2
Frontend 20241002.3
Current Node Red, add on Current version: 18.1.1
HACS Node-RED Companion Integration v 4.1.1
This is an example of what I tried:
Node Red > Hamburger menu > Manage Palette > Install
node-red-contrib-sonos-plus
A set of Node-RED nodes to control SONOS player in your local network.
6.9.0 5 months ago
After som time, this message appears:
"Failed to install: node-red-contrib-sonos-plus
Install failed
Check the log for more information":
Event log
-----------------------------------------------------------
2024-10-17T07:18:59.666Z Install : node-red-contrib-sonos-plus 6.9.0
2024-10-17T07:18:58.084Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --omit=dev --engine-strict [email protected]
2024-10-17T07:19:20.685Z [err] npm warn deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
2024-10-17T07:19:20.743Z [err] npm warn deprecated [email protected]: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
2024-10-17T07:19:21.081Z [err] npm warn deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
2024-10-17T07:19:25.222Z [err] npm warn tarball tarball data for ftpd@git+ssh://[email protected]/biddster/nodeftpd.git#0d299f78af7f0006a9d5a084614bd8b56a369d1b (null) seems to be corrupted. Trying again.
2024-10-17T07:19:28.050Z [err] npm warn tarball tarball data for ftpd@git+ssh://[email protected]/biddster/nodeftpd.git#0d299f78af7f0006a9d5a084614bd8b56a369d1b (null) seems to be corrupted. Trying again.
2024-10-17T07:19:44.800Z [err] npm error code ENOENT
2024-10-17T07:19:44.803Z [err] npm error syscall scandir
2024-10-17T07:19:44.803Z [err] npm error path /root/.npm/_cacache/tmp/git-cloneaCKJlg/fixture/jose/tricky_paths/b//s/l, ""q'u"o"te''; pi|p|e & ^up^
2024-10-17T07:19:44.805Z [err] npm error errno -2
2024-10-17T07:19:44.818Z [err] npm error enoent ENOENT: no such file or directory, scandir '/root/.npm/_cacache/tmp/git-cloneaCKJlg/fixture/jose/tricky_paths/b//s/l, ""q'u"o"te''; pi|p|e & ^up^'
2024-10-17T07:19:44.818Z [err] npm error enoent This is related to npm not being able to find a file.
2024-10-17T07:19:44.818Z [err] npm error enoent
2024-10-17T07:19:44.830Z [err]
2024-10-17T07:19:44.831Z [err] npm error A complete log of this run can be found in: /root/.npm/_logs/2024-10-17T07_18_58_850Z-debug-0.log
2024-10-17T07:19:45.043Z rc=254
What’s the problem?