Hello everyone!
Unfortunately, no node updates are possible for me.
Examples:
a) node-red-contrib-opcua from 0.2.291 to actuel 0.2.292
b) node-red-dashboard from 3.2.0 auf actuel 3.2.3
It is also not possible to uninstall unused nodes.
My system:
This is a known npm related issue that occurs occasionally, but the cause has not so far been identified. If you go to the folder /data/node_modules/ and delete any folders starting with a dot and then try again, you should be ok.
What directory is that? where is that? It doesnt look right at all. There should not be a .package-lock file there.
looking at the path /data/xxx mentioned in the logs, it suggests this is a docker image? If so, did you enter the terminal for that container? or go to the mapped path for /data/?
You are not very forthcoming with details! It makes it hard to help & makes us ask more and more questions, over and over! For example...
What "did not have the desired success"?
What did you actually do?, what command did you issue?, what result did you see? did you check the directory was present & that is was gone after deletion?
Ummm "yes" what? What does that image show me? That could be the screenshot of any directory in the world - not only that, it doesnt show me what directories do or do not exist (only that there are at least 3 things inside (one of which is cut off)).
Anyhow, moving on.
Let me put it this way.
If NPM fails and tells you ENOTEMPTY: directory not empty, rename '/data/node_modules/node-red-contrib-opcua' -> '/data/node_modules/.node-red-contrib-opcua-ABCDEFG' then you need to delete '/data/node_modules/.node-red-contrib-opcua-ABCDEFG' then try install again.
as described in the introduction, I use nodered in a docker container. so I'm assuming everything is happening inside the docker-container.
as recommended before the last installation I have the folders:
.bin and
.node-red-contrib-opcua-PzFixMVZ
both deleted
(the small picture should demonstrate this)
and then restarted the nodered container
only now have I triggered the update "node-red-contrib-opcua".
the last log documented the result
Do you mean the folder has come back again?
No need to restart the container by the way.
Delete it and make sure it is not there immediately before you attempt the node update.
Are you sure? ls -a may not show dot files first, depending on your collate settings.
Scroll down to that exact folder name to make sure. Or run ls -d \.*
An alternative is to use the sledgehammer. Remove (or rename) /data/node_modules completely and restart node-red and make sure it fails to run due to the missing modules. Then, in the /data folder run npm install
which will rebuild it.
[Edit] On second thoughts definitely rename, don't delete, in case it is a disaster. I am not sure whether node-red itself is installed inside that folder and whether npm install would re-install it.
Thank you again for your support.
Using the Docker concept has proven to be the fastest and most effective way.
Created a new Node-red container with a new volume, downloaded the repository, reinstalled and set up nodes, and lo and behold, it's working.