package.json updater script

[jacbn]

When reviewing dependencies for updates, we often run yarn update-interactive or yarn audit etc. These do not check/update the version numbers specified in package.json, but rather the versions in yarn.lock (those actually used when running yarn). There is no real issue with this, but it means package.json, which would otherwise be a very easy way to check what versions of dependencies we have installed, is often out of date and is not a reliable reference. As some simple housekeeping, I have created a script to go through the genuinely-used versions in yarn.lock and, if there is a discrepancy, print this to the console for manual checking/updating.

[jacbn]

Some thoughts:

• Should scripts exist in a /scripts directory? There are a few we could move now (the release scripts should probably stay where they are) to clean up the root.
• Should this update the versions automatically or is it best to keep it manual?

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 41.69%. Comparing base (0ec4377) to head (e465fc4).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1834   +/-   ##
=======================================
  Coverage   41.69%   41.69%           
=======================================
  Files         542      542           
  Lines       23683    23683           
  Branches     7855     7856    +1     
=======================================
  Hits         9874     9874           
  Misses      13765    13765           
  Partials       44       44           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.