chore(monorepo): bump required Node.js version to match electron environment

[gribnoysup]

Last time we were doing major electron upgrade, we forgot to bump required node version to match. This is just a minor one this time, so not that big of a deal, but it's helpful to keep it in sync to make sure that the tests are running in the same env that the app is running

[codeowners-service-app]

Assigned lerouxb for team compass-developers because mabaasit is out of office.

[gribnoysup]

Seems like this minor bump reveals an issue somewhere in our units:

ReferenceError: require is not defined in ES module scope, you can use import instead

Moving to draft for now to take a closer look

[addaleax]

@gribnoysup I'd actually check whether this also appears with the latest Node.js 22.x version, this sounds like a familiar bug in Node.js's ESM compatibility that has actually been fixed in more recent versions

[gribnoysup]

Oh, interesting! I'll check, thanks for the pointer!

[nbbeeken]

Can you also update .tool-versions?

[gribnoysup]

Same on latest 22, not exactly sure yet what's going on, but seems like in these Node.js versions some ts files are not passed through the ts-node anymore when mocha is running, looking a bit deeper

[gribnoysup]

Oufff, okay, seems like in Node.js 22.15 what was happening is:

1. mocha would try to load a .ts file as esm first
2. this would fail with Unknown file extension
3. mocha will fallback to require
4. ts-node register for mocha will kick in, parse the file, everything is now commonjs there
5. mocha is happy and running the test

In Node.js 22.18+ (maybe slightly earlier, I haven't tracked to exact version) .ts is now a known extension, so step 2 doesn't fail, Node.js will try to parse the file, ts-node/register doesn't kick in (because we haven't configured it for esm yet?), there's this mix of esm / require that Node.js detects, importing a file fails with unrecoverable error, mocha fails