Hi, all. First post here, searched for similar questions, didn't find any.
I am interested in version pinning for external packages (those in Setup tab of Function node).
Tried to use "package@version" notation, in a losing effort.
Is there a way to pin/fix version of external package?
Sometimes "current version" is not a perfect solution.
It's not very clear, what version I get if I import flow on fresh installation.
NPM registry is not the safest supply chain on the planet.
It can be compliance issue (itsec people hate when versions not nailed down)
If you are using the palette manager in the Editor then that is designed to be as simple and robust to use as possible I believe. If you want to do something outside its features, you will need a command line on the Node-RED server. From there, go to your Node-RED userDir (usually ~/.node-red) and you can then use standard npm commands and/or edit your package.json file to pin versions as needed.
Just note that I think that if you later update something from the palette manager, I don't know whether it simply updates to the latest or whether it respects your package.json - you may wish to check that.
Yeah, I am not very good at js/ts right now (backend background), so I won't be bothering core devs with a feature request, until I have a quality PR to back it )
I think I will return to this question in the future.