I've been running node-red successfully for years despite not knowing a thing about linux. After updating a palette yesterday (don't remember which one) the editor won't load anymore. It's eternally stuck at "Loading Nodes 43/97", even after restarting the service, rebooting the device, emptying browser cache etc.
I tried using node-red --safe, and it looks good in the command line, but alas, the page still stalls at 43/97. I don't even get anyplace where I could do anything in the UI. I must be doing something wrong on a very basic level. But what? Any ideas?
Edit: when I start it as a service, the log is throwing constant errors regarding a node 2427. It could be unrelated, but maybe that's the culprit somehow. But how can I disable a particular node if the editor doesn't launch? Is there some kind of flag that I could use to disable a particular node or module?
(node:2427) UnhandledPromiseRejectionWarning: Unhandled promise rejection. 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(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2) 20 Oct 14:22:58 - [warn] [miio-airpurifier-input:Pollen] Miio Airpurifier Error: Could not connect to device, handshake timeout (node:2427) UnhandledPromiseRejectionWarning: Error: Could not connect to device, handshake timeout at Timeout._onTimeout (/home/pi/.node-red/node_modules/miio/lib/network.js:427:17) at listOnTimeout (internal/timers.js:554:17) at processTimers (internal/timers.js:497:7)