Test with Node 20, updated deps + js-wacz

[matteocargnelutti]

How I tested these changes:

• docker compose up -d --build to force a rebuild

• In the web container's shell:

  • npm run build does generate valid (?) bundles
  • invoke run successfully runs npm run build
  • npx js-wacz --help prints js-wacz's help menu

  Tests are passing and the app behaves normally when tested locally.

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 71.22%. Comparing base (6b447bc) to head (efa78c0). Report is 1 commits behind head on develop.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## develop #3486 +/- ## ======================================== Coverage 71.22% 71.22% ======================================== Files 48 48 Lines 6512 6512 ======================================== Hits 4638 4638 Misses 1874 1874 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[rebeccacremona]

This looks great!!!

I tested by:

• Removing my local node_modules folder, to make sure it didn't accidentally sync a cache of the old dependencies into the container
• Removing the perma_node_modules volume, for the same reason
• Checking out your branch
• Adding a test-node-dependencies suffix to the web image's tag to force a rebuild without clobbering the 105-28fef2ca2ecd1c74ba3059f0b59a4d34 image
• docker compose up, and watching the build
• docker compose exec web invoke run, with CELERY_TASK_ALWAYS_EAGER = False
• Doing a side-by-side comparison of the CSS on the Perma dashboard with prod
• Running through all of the javascripty parts of the app:
• • making a new folder
• • renaming an existing folder
• • moving a link between folders
• • viewing an old link batch
• • making a new link batch
• • switching folders using the folder tree
• • switching folders using the dropdown
• • expanding and collapsing a link's details in the link list
• • the "upload your own" flow
• • changing a link's options using the controls in the "tray" on the playback page
• • clicking through each tab of the /manage/stats page

I can't think of anything else to check!!

[jcushman]

This is awesome -- I think ship it if Ben is happy? As Becky points out we use pre-built assets in production, so the testing she did is likely to have found any problems that might exist.

[matteocargnelutti]

Thank you all for having a look and for the helpful feedback 👋