To find the available version you can use list or info. Not the installed version.
On a 2.1.4 install the command returns...
2.2.2
On a 2.2.2 install the command returns...
$ npm list -g node-red
/usr/local/lib
└── (empty)
$ npm list node-red
node-red-project@0.0.1 /home/pi/.node-red
└── (empty)
So, that specific command does not show the installed version at all. Where as my old command on older installations worked...
On older 2.1.4...
# npm ls -g --depth=0 | grep node-red | cut -d '@' -f 2
2.1.4
On 2.2.2...
# npm ls -g --depth=0 | grep node-red | cut -d '@' -f 2
(Nothing Results)
$ npm ls --depth=0 | grep node-red
node-red-project@0.0.1 /home/pi/.node-red
├── node-red-contrib-bme280@1.0.0
├── node-red-contrib-counter@0.1.6
├── node-red-contrib-cron-plus@1.5.6
├── node-red-contrib-fs-ops@1.6.0
├── node-red-contrib-linux-network-stats@0.2.5
├── node-red-contrib-loop-processing@0.5.1
├── node-red-contrib-md5@1.0.4
├── node-red-contrib-os@0.2.1
├── node-red-contrib-play-audio@2.5.0
├── node-red-contrib-ring-buffer@0.10.0
├── node-red-contrib-simple-gate@0.5.2
├── node-red-contrib-traffic@0.2.1
├── node-red-contrib-ui-led@0.4.11
├── node-red-dashboard@3.1.5
├── node-red-node-mysql@1.0.0
├── node-red-node-pi-gpio@2.0.1
├── node-red-node-pi-gpiod@0.4.0
├── node-red-node-ping@0.3.1
├── node-red-node-random@0.4.0
├── node-red-node-serialport@0.15.0
├── node-red-node-smooth@0.1.2
├── node-red-node-ui-list@0.3.6
├── node-red-node-ui-table@0.3.12
(Of course none of the above are 2.2.2)
This is either because something changed with how deployment is done, presented, or something has changed with how npm or such works, or whatever the case. It does not change the fact or issue that NR should have some way via CLI or node, to report its current installed version information.
So, my questions stands... how does the wire editor know what version is installed, is it a static value? Or dynamic determined? Is there some way to present that information other than using npm? Or if npm is the only option? How can one find such that is not a human action dependent sequence? Something via CLI, that automation can invoke is what is needed. If there is a CLI method that works, like before, I can do the rest, via Ansible or whatever.
