This is an npm error that pops up occasionally. Delete the folder /home/pi/.node-red/node_modules/.node-red-dashboard-LM9EixDS and try again. If you get further similar messages delete those too.
Hi - I have just republished v3.2.3 that doesn't have some dev libraries cruft in there - so should install much more quickly... and hopefully less error prone.
Those are not all related to the dashboard. It is normal to have lots there. You can safely delete all the .* files. They should not be there.
Also, even if you do mess up your node_modules folder it is easy to recover it. You can delete it and go into the .node-red folder and run npm install
to rebuild it.
It installed the old version because the file package-lock.json tells npm the exact versions that should currently installed. What happens if you now try to install the latest by npm install node-red-dashboard@3.2.3
Do that in the .node-red folder
added 228 packages, and audited 229 packages in 10s
30 packages are looking for funding
run `npm fund` for details
7 vulnerabilities (2 low, 3 moderate, 1 high, 1 critical)
To address issues that do not require attention, run:
npm audit fix
Some issues need review, and may require choosing
a different dependency.
Run `npm audit` for details.
# npm audit report
engine.io 4.0.0 - 6.2.0
Severity: high
Uncaught exception in engine.io - https://github.com/advisories/GHSA-r7qp-cfhv-p84w
fix available via `npm audit fix`
node_modules/engine.io
got <11.8.5
Severity: moderate
Got allows a redirect to a UNIX socket - https://github.com/advisories/GHSA-pfrx-2q88-qq97
No fix available
node_modules/got
public-ip 2.1.0 - 4.0.4
Depends on vulnerable versions of got
node_modules/public-ip
node-red-contrib-ip *
Depends on vulnerable versions of public-ip
node_modules/node-red-contrib-ip
xmldom *
Severity: critical
Misinterpretation of malicious XML input - https://github.com/advisories/GHSA-5fg8-2547-mr8q
Misinterpretation of malicious XML input - https://github.com/advisories/GHSA-h6q6-9hqw-rwfv
xmldom allows multiple root nodes in a DOM - https://github.com/advisories/GHSA-crh6-fp67-6883
No fix available
node_modules/xmldom
edimax-smartplug *
Depends on vulnerable versions of xmldom
node_modules/edimax-smartplug
node-red-contrib-smartplug *
Depends on vulnerable versions of edimax-smartplug
node_modules/node-red-contrib-smartplug
7 vulnerabilities (2 low, 3 moderate, 1 high, 1 critical)
To address issues that do not require attention, run:
npm audit fix
Some issues need review, and may require choosing
a different dependency.
pi@ubuntu:~/.node-red$ npm install node-red-dashboard@3.2.3
changed 1 package, and audited 259 packages in 4s
47 packages are looking for funding
run `npm fund` for details
4 vulnerabilities (3 moderate, 1 high)
To address issues that do not require attention, run:
npm audit fix
Some issues need review, and may require choosing
a different dependency.
Run `npm audit` for details.
Don't do that, it may install versions of packages which nodes have not been tested with.
As for the vulnerabilities it is not an issue unless your node-red is open to the internet. I don't worry about it, I assume that if there were any significant issues then the core team would be on it.
after reboot Node-Red says 3.2.2
