chore: bump deps blocked by ESM

[Lemonexe]

Description

After bumping node to 24 in #23206, all our CJS–ESM pains have been washed away, magically solved in nodeJS nodejs/node#51977, so now everything will be 🌈 and 🦄 ❤️

Problems were mainly in these domains:

• electron-main
• playwright test runtime (not to be confused with the tested app, which runs in browser)
  • FYI: we don't transpile or bundle our test runtime files, because playwright has a TS loader, something like tsx, so we're loading TS files, which are written in ES, but the TS loader transpiles them on the fly to execute them in nodeJS in CJS mode
    • playwright can run in ESM mode, but support is experimental and I haven't made it work.
  • executing test files that import ESM only packages was not possible until node 24, now it just works 🎉
• jest easily solvable by babel using this approach. This is already done a lot in mobile..
  • Note that this is nothing new, we could have done this always
• metro, not really solved, just hacked 😕

And so I bumped all packages that were considered blocked:

• electron-store (electron-main)
• @noble/curves (electron-main, playwright)
• uuid (playwright)
• chalk (electron-main, some scripts)

QA instructions

desktop builds here

Suite Desktop: on Win, macOS, Linux, test that these settings are correctly persisted (electron-store):

• ℹ️ just FYI: electron-store is not the primary storage of userdata, that's IDB which is both for Web & Desktop. Only some specific data that are related to Desktop app behavior in relation to OS are stored in electron-store
• Need to test at least some of the settings, that they are correctly persisted after app relaunch
  • window size
  • biometric authentication enabled/disabled
  • tor enabled/disabled
  • bridge choice
  • theme choice

Suite Desktop, Web, Android, iOS (@noble/curves)

• device authenticity check, please test production TS7 on
• evolu getProofOfDelegatedIdentity how to test??

Also uuid: Not much to test, it's a tiny utility hidden beneath. Testable is only desktop/web Message system manager (correctly generates random uuid).

And some CI scripts which I have all tested:

yarn check-workspace-resolutions
yarn workspace @suite-common/icons generate-icons
yarn update-project-references
yarn generate-package @suite-common/blabla

And green CI means Playwright and Jest is OK 💚

Related issue

Resolve #22316
Resolve #14482

Notes

Actually, this nodeJS feature was even backported to 22.12, so we could have done it much sooner 🤦 But we were staying on 22.11 for the past year, and I only realized that now.. This is however highly relevant for electron-main, because electron-main environemnt is driven by electron, not by our repo. Electron ships with node 22.20 as of 39. That's why I electron store can be loaded in CJS mode, and again, it's something I could have done sooner, probably at electron 35?

Note that long-term, we might still want to bundle our Electron-main script as ESM, and run it as such. That would require abandoning webpack in electron-main, probably rollup instead. But it's not so hot now..

🔍🖥️ Suite desktop test results: View in Currents

🔍🖥️ Suite web test results: View in Currents

🔍🖥️ Suite native android test results: View in Currents

[trezor-bot]

✅ Previously successful run of [Test] PR Suite Desktop e2e tests workflow has been found.
⏭️ Skipping tests for this run.
💡 If you are unsure about your latest changes, please rerun the workflow manually. (Use the Re-run all jobs option)

[trezor-bot]

✅ Previously successful run of [Test] PR Suite Web e2e tests workflow has been found.
⏭️ Skipping tests for this run.
💡 If you are unsure about your latest changes, please rerun the workflow manually. (Use the Re-run all jobs option)

[Lemonexe]

Otherwise you get

Android Bundling failed 47120ms suite-native/app/index.js (8598 modules)
Unable to resolve "uuid" from "suite-common/message-system/src/messageSystemUtils.ts"

[peter-sanderson]

[Lemonexe]

deleting this effectively means changing to module: ESNext and moduleResolution: nodenext
(inheriting from tsconfig.base.json)

I don't know for what historical reason was it necessary to specify CJS module resolution for typescript, but now it isn't, because /src si bundled and /e2e is loaded via playwright typescript loader, which resolves ESM and CJS mostly quite well.

[Lemonexe]

this couldn't have worked, because node_modules/\@noble does not exist,
so the ?! would never match
so the pattern would never match
so all node_modules would be ignored from babel transform = same as default.

Well, this means it was not needed 🙂

[Lemonexe]

superfluous; this is the default. Deleting this line so it uses the default in jest.base.config.js

[peter-sanderson]

gigachad 🐶