Hi (again) Nick.
Ok. But "how" this presented itself to me was ....... confusing.
And I apologise for calling them ERRORS, rather than warnings. I know there is a big difference but that part of me which saw them flagged them as needing attention.
I'll get to that shortly.
So, the time line of what was/is going on:
I installed NR, way back when.
I installed nodes.
I kept most of the nodes up to date.
Updating them seldom required restarts. This was good as I could start at the top of the list and work my way down. (Note this is 99% done on REMOTE machines.)
I updated to a newer version of NR.
I tried to keep nodes up to date.
I installed some nodes in a trial for things but it didn't work always.
Sometimes I removed them, other times not. I saw some potential for future use.
Recently NR updated to 19.4. Woo Hoo - I think is the general feeling.
The new edit screens and a few bugs fixed. It was good.
My NR skills have come on somewhat from what they were at the start. Sure I am still learning. But I believe the only time you don't learn is when you are dead. No one knows EVERYTHING.
My RPI population has somewhat grown and I have 9 RPIs on my network doing their own little job.
I know I said 10. Sorry.
One of the RPIs is my NTP server and WAP. It is on 24/7. Its connection to the net is only when it is needed.
Anyway, I thought it would be a good time to get them all "on the same page" so if/when I am designing a flow, it can work on any/all of them.
A few weeks ago I powered them all up and make sure they were 19.4.
A few days ago I decided to get them all 100% up to date. Unknown to me the time it will take.
(Stating how it happened here. No blame allocated.)
Rather than being able to open the Manage palette and start at the top and scroll through and update the nodes as needed, just about every node upon updating told me I needed to restart NR.
I don't know the finer details of that, and being a remote machine, a reboot seemed simpler.
(Too many notes. Yeah, I shall have to file the NR restart command better, but anyway...)
Also to my detriment: I am not sure I can update "all" the nodes (requiring a restart) and do ONE restart to get them all up to date. What ever. Academic now.
While going through the list I saw "rbe" said it was needing updating. Strange. I have seen it doesn't always meet my needs, but it could be useful so I will update it.
While going through the list, I also saw "twitter", "serial-port", "telegram" and other weird ones also needed updating and/or had red triangles on them. Huh?
So I have 9 RPI's sitting there (well: 8 as the NTP one is pretty well up to date and is an OLD RPI. Rebooting it is painfully slow.)
I asked about the rbe problem and was pointed to "uninstall it and the new version of NR will fix it." was basically what I read.
I went through uninstalling all the rbe nodes on all the machines.
Some came back happily and there was no other things said.
They would then be rebooted and (I think) rbe would then be happy and up to date.
Others would complain and I would get warnings in one format.
Others would complain (probably about the same stuff) but in a different format. Huh?
One of them told me to update npm also. Ok......
So, all the uninstalls done, some now happy with rbe. Some not.
That got me to "you shouldn't have un-installed them, simply install the new version." (implied from npm.)
Ok, tried that.
More new warnings and messages. What can of worms have I opened?
NR says to run npm audit fix to resolve the problems/warnings/incompatibilities.... What ever...
So I seemed to have opened another can of worms.
I have a couple of machines which are not up to date with rbe.
I see (from dceejay) that I don't need to update them as the update was to do with Japanese locale stuff. Good.
The "twitter", "email" (don't know why I forgot that one), "feed-parser", "ping", "serial-port" and a couple of others are not up to date.
I get that NR is an "amalgamation" of programs/stuff to make the bigger thing.
But I am at a loss why "twitter" can't be removed/un-installed. As I don't need/use it (I hope I never need it.) Having it in the package is leaving an attack vector open. Isn't it?
Sure, I can/will get around to disabling it soon.
Looking at the bigger picture:
So with NR 2.x coming soon and the dependency on the earlier stuff (node.js) will be removed....
That will fix the update stuff?
I'd better stop here. I am becoming distracted/disoriented to where I am wanting to go and where I am going.
But this is also (I hope) an external view of how this (what ever "this" is) happened and maybe a bit of help to anyone else like me: a noob.