Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation

[tbully]

Hello All -

I was running an embarrassingly old version of MSR (26011) and just upgraded to latest-26193-50401535 bare metal.

I've read the change logs and do see considerable drift so I kind of expected a few issues. I did run "npm run deps" prior to restart and have since ran it again just in case.

Currently running node 22.2.0

My rules apparently are running in the background. However, the UI doesn't show any of my "rooms", rules, reactions, or anything on the status screen. Thoughts?

[tbully]

Forgot logs. There were pages of logs upon initial restart. In fact, the logs rolled four times! However, I'm seeing this rather persistent message:

[latest-26193]2026-08-01T11:05:42.200Z MessageBus:ERR MessageBus: SystemController#reactor_system notification handler threw error: [Error] require() of ES Module /home/tbully/reactor/node_modules/devalue/index.js from /home/tbully/reactor/server/lib/util.js not supported.
Instead change the require of index.js in /home/tbully/reactor/server/lib/util.js to a dynamic import() which is available in all CommonJS modules. [-]
[latest-26193]2026-08-01T11:05:42.200Z MessageBus:ERR MessageBus: bus System#reactor_system>system sender was System#reactor_system>system; ident SystemController#reactor_system; message { "sender": System(System#reactor_system>system), "currentSender": (seen=.sender), "type": "entity-changed", "data": (seen=.sender), "args": Array(0) [], "sentFrom": "Error: OK\n at System.publish (/home/tbully/reactor/server/lib/Observable.js:78:19)\n at System.markDirty (/home/tbully/reactor/server/lib/Entity.js:388:154)\n at System.setAttribute (/home/tbully/reactor/server/lib/Entity.js:526:212)\n at /home/tbully/reactor/server/lib/SystemController.js:309:82\n at /home/tbully/reactor/node_modules/diskusage-ng/lib/posix.js:13:13\n at ChildProcess.exithandler (node:child_process:413:7)\n at ChildProcess.emit (node:events:520:28)\n at ChildProcess.emit (node:domain:488:12)\n at maybeClose (node:internal/child_process:1105:16)\n at Socket.<anonymous> (node:internal/child_process:457:11)" }
[latest-26193]2026-08-01T11:05:42.200Z MessageBus:CRIT Error: require() of ES Module /home/tbully/reactor/node_modules/devalue/index.js from /home/tbully/reactor/server/lib/util.js not supported.
Instead change the require of index.js in /home/tbully/reactor/server/lib/util.js to a dynamic import() which is available in all CommonJS modules. [-]
Error [ERR_REQUIRE_ESM]: require() of ES Module /home/tbully/reactor/node_modules/devalue/index.js from /home/tbully/reactor/server/lib/util.js not supported.
Instead change the require of index.js in /home/tbully/reactor/server/lib/util.js to a dynamic import() which is available in all CommonJS modules.
at _0x39d5d3 (/home/tbully/reactor/server/lib/util.js:1526:39)
at System.serialize (/home/tbully/reactor/server/lib/Entity.js:638:53)
at SystemController.persistEntity (/home/tbully/reactor/server/lib/Controller.js:900:61)
at SystemController.notify (/home/tbully/reactor/server/lib/Controller.js:945:189)
at SystemController.notify (/home/tbully/reactor/server/lib/SystemController.js:427:31)
[latest-26193]2026-08-01T11:05:43.078Z wsapi:ERR wsapi: unparseable message from client "192.168.34.113#22": [Error] require() of ES Module /home/tbully/reactor/node_modules/devalue/index.js from /home/tbully/reactor/server/lib/util.js not supported.
Instead change the require of index.js in /home/tbully/reactor/server/lib/util.js to a dynamic import() which is available in all CommonJS modules. [-]
[{"jsonrpc":1,"id":2,"method":3,"params":4},"2.0",33,"reactor.systime",{"t0":5},1785582344121.1]

[gwp1]

What's the environment of your system? Docker, bare metal?

[tbully]

Always forget some detail! Bare metal. I made a tarball prior to upgrade and rolled back to that to recover. No rush but appreciate the quick response this morning!

[tunnus]

@tbully maybe not that helpful comment, but I strongly recommend docker (builds)

[toggledbits]

Did you update packages?

Edit: nodejs 22.2.0 is the problem. You should update nodejs to the latest LTS, or at least to nodejs v22.12.0. There is also a quicker workaround that may work: add --experimental-require-module to the nodejs command line that starts Reactor.

[therealdb]

I agree with @tunnus.
It's not that difficult and for (almost) critical systems I really appreciate the fact that each system is separate from the others, for maximum stability.

[toggledbits]

I was able to find a workaround, so build 26214, which will be posted shortly for bare-metal only, should address the issue without any changes to your system (other than the Reactor package).