Attempting to update to 3.x.x creates dependency and custom node install issues

[aMacDawg]

Expected outcome: as a user, I can set the latest version of Node-RED to "~3.0.2" (latest official release) from a prev version of 1.3.5, and any custom nodes as well as any custom npm modules referenced in the "add a module" section of the function node will install as expected

Current outcome: As a user, when deploying to a test branch with the latest Node-RED version ("~3.0.2"), certain custom npm packages break and are not able to be installed, with these errors:

"Installation of module node-red-node-rbe failed:"
10/24/2022, 3:01:02 PM
msg : string[42]
"------------------------------------------"
10/24/2022, 3:01:02 PM
msg : string[499]
string[499]
npm WARN config production Use `--omit=dev` instead.
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: [email protected]
npm ERR! notsup Not compatible with your version of node/npm: [email protected]
npm ERR! notsup Required: {"node":"0.10.x || 0.8.x"}
npm ERR! notsup Actual:   {"npm":"8.19.2","node":"v18.11.0"}

npm ERR! A complete log of this run can be found in:
npm ERR!     /app/.npm/_logs/2022-10-24T22_01_02_132Z-debug-0.log

Notes

From the discussion in this related stackoverflow post, it seems one of the initial causes of this issue is related to the nano package loading in the follow package which breaks npm which refuses to load it, citing it is too old.

Other issues seem to include Node itself being out of date, and the need for manually declaring each npm module added in the function nodes in the dependency KVP.

I was able to resolve my own known issues encountered by upgrading the Node-RED version by deleting the nano package kvp and adding the npm modules I reference in the "add module" feature in the function nodes as dependencies in the package.json file.