We've just published Node-RED 3.1.9.
This fixes the issues reported today where Node-RED would not start on Windows using the very latest Node 18 and Node 20 releases.
These releases of Node.js included a security fix related to running external processes on Windows. More specifically, they now explicitly block a particular combination of options in some circumstances. Unfortunately, the way we run npm from within Node-RED fell foul of exactly those circumstances.
We've applied a small change that gets us away from the now-blocked path and all looks good again.
For good measure, there are a few subflow-related fixes thrown in that were also ready to ship.
More details in the changelog.
