Upgrade Next.js and to remove the openssl workaround

[thomvaill]

We are running Next.js v10, while the current latest major version available is v14.

Next.js v10 runs Webpack 4, which uses a deprecated openssl hashing algorithm (md4) (#85).
A workaround was introduced:

• fix: workaround for ERR_OSSL_EVP_UNSUPPORTED build issue #114
• then Make Log4brains run on Node 18 and 20 #124
• and fixed by fix: lerna publish on Node 18-20 #125

But we should try to upgrade ASAP to get rid of this workaround.

Since we rely a lot on Next.js hacks (#NEXTJS-HACK comments in the code), the task does not look easy at all. Let's first assess if we should target to latest version, or a closer one, like v11 which introduces Webpack 5.

[thomvaill]

Blocks #4 since it may change the images behaviour

[omawhite]

@thomvaill hey is this still open? I was digging through the repo to try to see how hard this might be. So far i've got a draft PR, and i've got yarn build working locally, but I haven't done much else to verify if the upgrade is working so far.

[omawhite]

And a follow up question what version of node and yarn do you use while developing? I'm running into issues getting yarn link-cli to work even after adding export PATH="$PATH:$(yarn global bin)" to my .zshrc wondering if maybe it's because i'm not using the right version of yarn or something.

Here's what I've got

yarn lerna -v
5.5.2

yarn -v       
4.10.2

node -v
v22.14.0

Also FWIW i've got yarn installed through volta.