Unable to update or install palettes in Home Assitant Node Red

Third party integrations Node-RED
1

Hello,
I run HASIO on a Hyper-V virtual machine and everthing is up to the the latest version.
Whenever I try to update or install a new palette in my Node Red instance in Home Assitant, I get the following error:

2025-10-27T13:53:33.620Z Install : @node-red-contrib-themes/theme-collection 4.1.0

2025-10-27T13:53:34.405Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --omit=dev --engine-strict @node-red-contrib-themes/[email protected]
2025-10-27T13:53:34.569Z [err] npm warn Unknown builtin config "globalignorefile". This will stop working in the next major version of npm.
2025-10-27T13:53:34.569Z [err] npm warn Unknown builtin config "python". This will stop working in the next major version of npm.
2025-10-27T13:53:34.569Z [err] npm warn Unknown env config "globalignorefile". This will stop working in the next major version of npm.
2025-10-27T13:53:34.569Z [err] npm warn Unknown env config "python". This will stop working in the next major version of npm.
2025-10-27T13:53:36.455Z [err] npm error code EBADENGINE
2025-10-27T13:53:36.455Z [err] npm error engine Unsupported engine
2025-10-27T13:53:36.455Z [err] npm error engine Not compatible with your version of node/npm: @azure/[email protected]
2025-10-27T13:53:36.455Z [err] npm error notsup Not compatible with your version of node/npm: @azure/[email protected]
2025-10-27T13:53:36.455Z [err] npm error notsup Required: {"node":"10 || 12 || 14 || 16 || 18"}
2025-10-27T13:53:36.455Z [err] npm error notsup Actual: {"npm":"11.3.0","node":"v22.16.0"}
2025-10-27T13:53:36.455Z [err] npm error A complete log of this run can be found in: /root/.npm/_logs/2025-10-27T13_53_34_482Z-debug-0.log
2025-10-27T13:53:36.477Z rc=1

It seems that the version of NodeJS in HA is more recent then Node Red can accept and something with NPM, if I read this correctly
Is there a solution to this?
Regards, Chris.

2

You have installed a contrib node somewhere/sometime that has a dependency, ultimately, on @azure/[email protected]

This very old node demands Node.js as version 10,12,14,16 or 18 (it should have been written to ask for node: >=10). We are now well past v18. Everytime you try and do anything that uses npm, like update the palette, npm will check all dependencies and complain about the ‘bad engine’, and then stop.

As far as I remember (it was quite a while back) the finally discovered ‘best’ solution is to backup all the flows (carefully), remove Node-RED completely, and then reinstall from scratch.

https://community.home-assistant.io/t/node-red-problem-cant-update-or-install-palette-s/839821

Reinstallation should be accompanied by updating HA and the Node-RED Companion (integration) as well.

I don’t think the root cause of this was ever pinned down exactly, unless someone knows.

3

You can try looking through the dependent packages on npm for @azure/msal-node. Remove the package from your Node-RED setup thta uses it and everything should then fall back to working correctly.

Here’s the npm page for reference: https://www.npmjs.com/browse/depended/@azure/msal-node

edit:
Do you have any of these packages installed?

  • node-red-contrib-msgraph
  • node-red-contrib-azure-iothub-2-adt
  • node-red-contrib-microsoft-auth
  • node-red-contrib-microsoft-teams-tasks
  • node-red-contrib-msal
  • node-red-contrib-azure-ad-auth
  • node-red-contrib-azure-ad-login
4

You can try finding the upstream package causing the issue by running this command in an exec node (the exact directory may vary for your setup):

npm --prefix /addon_configs/a0d7b954_nodered ls @azure/msal-node