upgrade to node 20

[RayBB]

Closes #8257

This upgrades us to node 20!

Technical

We have to update bundlesize because it has a dependency that won't work with node 20. See this.

Testing

We have to rebuild the docker image and I'm having some trouble with that on my machine.
Maybe we can put it on testing?

Screenshot

Stakeholders

@cdrini

[RayBB]

bundlesize which relies on iltorb which is deprecated and doesn't work everywhere seems to cause the CI to fail. siddharthkp/bundlesize#320 (comment)

[codecov-commenter]

Codecov Report

Merging #8322 (55b1e3f) into master (1205b5f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #8322   +/-   ##
=======================================
  Coverage   16.66%   16.66%           
=======================================
  Files          83       83           
  Lines        4422     4422           
  Branches      757      757           
=======================================
  Hits          737      737           
  Misses       3202     3202           
  Partials      483      483           

[cdrini]

Awesome thank you @RayBB ! I'll need to find a way to build this image so you can test on it. Are you still having issues on mac? :/

Also just to confirm, is 20 the LTS version?

[RayBB]

@cdrini 20 will be the LTS version per this:

Node.js 20 will enter long-term support (LTS) in October, but until then, it will be the "Current" release

I'll try to build the image again and report the exact issue but until then I can use GitPod.

[RayBB]

@cdrini I was able to build it on GitPod (I didn't bother trying locally b/c I'm low on battery).
docker compose run --rm home node --version returns v20.8.0

Logging in works, editing author identifiers, the library explorer loads (but is empty as usual), and as far as I can tell everything seems fine. Is it possible to put this on testing for a few days and see if any issues pop up? Or are there any other parts we should explicitly test.

Because we use node/webpack just for building (and don't have a nodejs server) I feel issues should generally be caught at the build step if there were major ones.

[cdrini]

Ok was able to successfully build/put on testing! LGTM ty @RayBB !

This might cause some headaches with package-lock.json files being out-of-sync/incorrect for folks. Will do another deploy tomorrow so this goes out and everyone can pull the latest version down and run a npm i --no-audit get everything.