Inject node doesn't work

[S474N]

Current Behavior

First I have dead loop in log, NR restarted. Last thing in log is:
23 Apr 19:29:44 - [error] UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason #<Object> .

I suspected the node-red-contrib-home-assistant-websocket plugin, when I delete it, Nodered does start, I can connect to the web administration, but all the inject nodes are gray and cannot be started.

I tested downgrading the docker image or even changing it because of nodejs. I also tried restoring the data from the previous day, but all to no avail.

During testing, I also turned off HA, which runs on another HW, to exclude influence.

I also tried updating npm to the latest version, I tried "audit fix".

Now I don't know what else to try.

Expected Behavior

Working inject nodes.

Steps To Reproduce

Don't know

Example flow

paste your flow here

Environment

• Node-RED version: v3.1.9, v3.1.8 - docker version
• Node.js version: 14, 16, 18
• npm version: that are in official docker images
• Platform/OS: arm64/Raspbian Bookworm
• Browser: Chrome

[S474N]

Log from npm audit fix --force

https://pastebin.com/wmrssAkQ

Packages:

    "name": "node-red-project",
    "description": "A Node-RED Project",
    "version": "0.0.1",
    "private": true,
    "dependencies": {
        "http-cookie-agent": "~4.0.2",
        "node-red-configurable-ping": "^1.0.2",
        "node-red-contrib-alarm": "~1.4.0",
        "node-red-contrib-broadlink-control": "~2.1.6",
        "node-red-contrib-buffer-parser": "~3.2.2",
        "node-red-contrib-cpu": "0.0.4",
        "node-red-contrib-cron-plus": "~2.1.0",
        "node-red-contrib-float": "~1.0.3",
        "node-red-contrib-foxtrotnode": "~1.2.1",
        "node-red-contrib-home-assistant-websocket": "~0.64.0",
        "node-red-contrib-homeconnect": "~0.6.7",
        "node-red-contrib-homekit-bridged": "~1.6.1",
        "node-red-contrib-influxdb": "~0.7.0",
        "node-red-contrib-meross": "~2.3.1",
        "node-red-contrib-miio-roborock": "~2.3.4",
        "node-red-contrib-modbus": "~5.30.0",
        "node-red-contrib-moment": "~5.0.0",
        "node-red-contrib-netatmo-dashboard": "~1.0.0",
        "node-red-contrib-nut-ups": "~1.1.0",
        "node-red-contrib-tasmota": "~1.0.0",
        "node-red-contrib-telegrambot": "~15.1.9",
        "node-red-contrib-telnet-client": "~1.0.4",
        "node-red-contrib-timerswitch": "~1.4.0",
        "node-red-contrib-unifi": "~0.3.15",
        "node-red-contrib-yeelight-compat-hue": "~1.2.1",
        "node-red-contrib-zigbee2mqtt": "~2.7.1",
        "node-red-dashboard": "~3.6.5",
        "node-red-node-email": "~2.2.1",
        "node-red-node-pi-gpiod": "~0.4.0",
        "node-red-node-random": "~0.4.1",
        "node-red-node-rbe": "~0.5.0",
        "node-red-node-tail": "~0.4.0",
        "tough-cookie": "~4.1.2"
    }
}

[hardillb]

Running npm audit --fix in the docker container isn't going to change anything as the changes will be reverted when the container is restarted which will happen when Node-RED restarts

The inject buttons being disabled has been seen occasionally and can sometimes be down to the browser caching old versions of the frontend is files. Please ensure the browser cache is cleared

[S474N]

Already tested - also new private window, in EDGE, same problem.

[knolleary]

What version of node.js are you using? That suggests you are on an old version that doesn't support the Object.hasOwn api

[S474N]

Yes you're right. In desperation, I tried all versions, upgrade/downgrade, until I ended up on node.js v14, where at least the basic functioning of my home works.

I am convinced that the error is in my old installation and in a lot of unresolved dependencies right within npm. Unfortunately, I didn't have time to completely reinstall everything, including all plugins.