Yes, granted, it isn't what I said was being done, but........
Installing nodes from the web page is painful at best.
So I ssh into the machine, cd .node-red and install them from the cli/terminal.
While doing this npm "complained" and said I am using an old version and there is a new version to get. *1
That took me on a slight tangent as I updated it and got it's warnings about old nodes and vounrebilities with existing nodes.
"to fix these problems do: npm audit fix, or npm audit to look at the problems"
I shall accept my stupidity and just get the problems fixed. Seeing what npm audit says would be beyond me, so it doesn't seem like a smart thing to do.
I did what was stated.
Somewhere in doing that I got the message about "permission denied with access to bluebird'.
I posted seeking information on what is/was going on.
So (and I will be told again that this has been talked about before. I don't remember.) if when I use npm to install a node and npm says it should be updated....... why is this not a good thing to do?
from the history command this is about the time when I got the error.
You can see that I went off to find this "bluebird" and read the readme file.
Though you don't see the replies (obviously) I hope this is enough information to help someone help me understand where the confusion is.
npm install node-red-contrib-queue-gate
npm install node-red-contrib-simple-gate
npm install -g npm
ls -l blue*