Lock file maintenance

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: Branch creation - "before 4am on monday" in timezone US/Eastern, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[blarghmatey]

The failing JS test is due to changes in the moment dependency. The 2.29.2 release changes how locales are loaded, and the representation that is being rendered appears to be the Romanian version of "January", which leads me to believe that the locale is not being properly set.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[ChristopherChudzicki]

MomentJS

The failing JS test is due to changes in the moment dependency. The 2.29.2 release changes how locales are loaded, and the representation that is being rendered appears to be the Romanian version of "January", which leads me to believe that the locale is not being properly set.

The dependency was previously ^2.29.4, so I don't think 2.29.2 was the problem. I changed the dep to 2.29.4 so we'll still be using that version, but won't update to the recently-released 2.30.x

@types/react

We were also getting a build error from the staff dashboard because of conflicting @types/react versions.

Many of our dependencies in this repo specify @types/react: * as a dependency; we specify @types/react: ^17 to match the react version we use in staff dashboard. For details, see

• Bug: React 18 types broken since the type release a view hours ago facebook/react#24304 (comment)
• Allow peer dependencies with stricter version ranges microsoft/DefinitelyTyped-tools#433

Ideally, our deps would specify @types/react: * as a peer-dependency, so that they would defer to our version rather than installing their own. In some cases, newer (major) versions of our dependencies do specify @types/react in this way. So this issue would probably improve with sufficient updates.

In the meantime, I forced yarn to resolve to @types/react: 17.

[ChristopherChudzicki]

A limitation of this is that yarn resolutions must be specified in the root package.json. So if we had differing versions of react (we do) AND multiple both versions used typescript (they don't) this could be problematic.