hi for some reason i cant update or add new nodes i just get the message
2023-08-08T18:56:16.282Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict @firstname.lastname@example.org
2023-08-08T18:56:17.214Z [err] npm
2023-08-08T18:56:17.215Z [err] WARN
2023-08-08T18:56:17.215Z [err] config production Use `--omit=dev` instead.
2023-08-08T18:56:18.650Z [err] npm
2023-08-08T18:56:18.651Z [err] ERR!
2023-08-08T18:56:18.651Z [err] Cannot read properties of undefined (reading 'isStream')
2023-08-08T18:56:18.658Z [err] npm
2023-08-08T18:56:18.658Z [err] ERR!
2023-08-08T18:56:18.658Z [err] A complete log of this run can be found in: /home/pi/.npm/_logs/2023-08-08T18_56_17_146Z-debug-0.log
any help would be great thanks
hi i was trying from the palette manager then tried from the pi
when i try (npm install @korve/node-red-convert-unit) on pi i get
pi@raspberrypi:~ $ npm install @korve/node-red-convert-unit
npm ERR! Cannot read properties of undefined (reading 'isStream')
npm ERR! A complete log of this run can be found in: /home/pi/.npm/_logs/2023-08-08T19_23_49_113Z-debug-0.log
node version v18.17.0
npm version 9.6.7
as for one assistant or docker dont think so
As a matter of interest, why did you go into that folder to run that? It doesn't make any difference for that command, but I just want to make sure you did not think I meant that folder for manually installing.
Were you previously able to install nodes? If so did you do anything that might have triggered the problem? Updated nodejs for example. Had a sudden power down? Is the system mis-behaving in any other way?
Can you show us the node-red startup log please. It probably won't help, but I am running out of ideas. You can see that by running
Copy/paste the text please rather than screenshot.
You could try re-installing nodejs sudo apt remove --purge nodejs sudo apt install nodejs
hi its been a while since i installed any nodes ,
i tried sudo apt remove --purge nodejs sudo apt install nodejs
made no diference unfortunately.
still cant install nodes,
is it worth removing node red and rinstalling,
the startup log showed -
Once Node-RED has started, point a browser at http://192.168.0.107:1880
On Pi Node-RED works better with the Firefox or Chrome browser
Use node-red-stop to stop Node-RED
Use node-red-start to start Node-RED again
Use node-red-log to view the recent log output
Use sudo systemctl enable nodered.service to autostart Node-RED at every boot
Use sudo systemctl disable nodered.service to disable autostart on boot
To find more nodes and example flows - go to http://flows.nodered.org
Starting as a systemd service.
8 Aug 22:53:10 - [info]
Welcome to Node-RED
8 Aug 22:53:10 - [info] Node-RED version: v3.0.2
8 Aug 22:53:10 - [info] Node.js version: v18.17.0
8 Aug 22:53:10 - [info] Linux 6.1.21-v8+ arm LE
8 Aug 22:53:12 - [info] Loading palette nodes
8 Aug 22:53:15 - [info] Dashboard version 3.5.0 started at /ui
8 Aug 22:53:16 - [info] Settings file : /home/pi/.node-red/settings.js
8 Aug 22:53:16 - [info] Context store : 'default' [module=memory]
8 Aug 22:53:16 - [info] User directory : /home/pi/.node-red
8 Aug 22:53:16 - [warn] Projects disabled : editorTheme.projects.enabled=false
8 Aug 22:53:16 - [info] Flows file : /home/pi/.node-red/flows.json
8 Aug 22:53:16 - [info] Server now running at http://127.0.0.1:1880/
8 Aug 22:53:16 - [warn]
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
8 Aug 22:53:16 - [info] Starting flows
8 Aug 22:53:16 - [info] Started flows
8 Aug 22:53:16 - [info] [mqtt-broker:dc0340c9643bd396] Connected to broker: mqtt://192.168.0.107:1883
thanks so much for the help its much apreciated