Node-red 1.2.0 won't start

Hi.
First of all, thank you for this great update on node-red.
After installing node-red 1.2.0, node-red won't start, giving me this error:

internal/modules/cjs/loader.js:548
throw e;
^

Error: Package exports for '/usr/local/lib/node_modules/node-red/node_modules/async-mutex' do not define a valid '.' target
at resolveExportsTarget (internal/modules/cjs/loader.js:545:13)
at applyExports (internal/modules/cjs/loader.js:459:14)
at resolveExports (internal/modules/cjs/loader.js:508:12)
at Function.Module._findPath (internal/modules/cjs/loader.js:577:20)
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:879:27)
at Function.Module._load (internal/modules/cjs/loader.js:785:27)
at Module.require (internal/modules/cjs/loader.js:956:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object. (/usr/local/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/api/flows.js:37:13)
at Module._compile (internal/modules/cjs/loader.js:1063:30) {
code: 'MODULE_NOT_FOUND'

I'm updating from 1.1.3 to 1.2.0 a VM on Debian.
Node version is v13.1.0
I reverted to 1.1.3 for now.
It should be something in the async-mutex module, but it should not crash in this manner.
Have i missing something?
Thanks.

What version of node.js are you using?

Node is v13.1.0

Looks like a known issue with the 13.x Node.js stream - a stream we don't support as it isn't a stable release.

Thank you. I'll update to 14 this night.
Many thanks.

Once you update nodejs you will have to re-install node-red and go to your .node-red folder and run
npm rebuild

1 Like

Those steps are always required right? For any update of node.js outside of the official script. Suspect so... time to update my notes!

Updating node to 14 worked.

Yes.
In fact whether you need the rebuild does depend on which nodes are installed, many nodes don't have a build step, but safest just to run it.
The script does the rebuild automatically.

Cool, still learning!