NodeJS v20.14 and @azure/msal-node@1.18.3 not supported

[Flashmajstr]

2024-06-07T07:19:42.716Z Install : node-red-dashboard 3.6.5

2024-06-07T07:19:42.731Z npm.cmd install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-dashboard@3.6.5
2024-06-07T07:19:43.175Z [err] npm warn config production Use --omit=dev instead.
2024-06-07T07:19:44.938Z [err] npm error code EBADENGINE
2024-06-07T07:19:44.939Z [err] npm error engine Unsupported engine
2024-06-07T07:19:44.939Z [err] npm error engine Not compatible with your version of node/npm: @azure/msal-node@1.18.3
2024-06-07T07:19:44.939Z [err] npm error notsup Not compatible with your version of node/npm: @azure/msal-node@1.18.3
2024-06-07T07:19:44.939Z [err] npm error notsup Required: {"node":"10 || 12 || 14 || 16 || 18"}
2024-06-07T07:19:44.939Z [err] npm error notsup Actual: {"npm":"10.8.1","node":"v20.14.0"}
2024-06-07T07:19:44.944Z [err] npm error A complete log of this run can be found in: C:\Users\mcz_JISGlate2\AppData\Local\npm-cache_logs\2024-06-07T07_19_43_058Z-debug-0.log
2024-06-07T07:19:44.976Z rc=1

• Node-RED-Dashboard version: 3.6.1
• Node-RED version: 3.1.9
• node.js version: 20.14
• npm version: 10.8.1
• Platform/OS: Windows
• Browser: Edge

[knolleary]

Hi @Flashmajstr

The module @azure/msal-node is not a module that node-red-dashboard depends on. You must have already had that installed within your node_modules directory.

You can find out what module depends on that by going to your .node-red user directory and running npm list @azure/msal-node.

[Flashmajstr]

node-red-project@0.0.1 C:\Users\mcz_JISGlate2.node-red
-- node-red-contrib-mssql-plus@0.12.2 -- mssql@10.0.1
-- tedious@16.5.0 -- @azure/identity@2.1.0
`-- @azure/msal-node@1.18.3

Hi, I have found out that, but still it's not allow me to upgrade node-red dashboard. Only what is working is downgrade to node.js 18.20 and afterwards both can be updated.

[knolleary]

This is not specific to node-red-dashboard.

Any task that runs npm install, for any module, will cause npm to spot the engine mismatch with that module and fail. There is nothing the node-red-dashboard module can do about that.