fix(deps): update dependency react-merge-refs to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-merge-refs	^1.1.0 -> ^2.0.0

---

Release Notes

gregberge/react-merge-refs (react-merge-refs)

v2.1.1

Compare Source

v2.1.0

Compare Source

Features

• allow a ref to be undefined in the types (#​33) (d9079dd)

2.0.2 (2023-05-09)

Bug Fixes

• move types condition to the front (#​30) (c91c4e4)

2.0.1 (2022-06-27)

Bug Fixes

• esm: add default export to maximize compat (8189083), closes #​27

v2.0.2

Compare Source

v2.0.1

Compare Source

v2.0.0

Compare Source

⚠ BREAKING CHANGES

• The package now exports ESM only and a named export.

Before:

import mergeRefs from "react-merge-refs";

After:

import { mergeRefs } from "react-merge-refs";

Features

• ESM only & named export (a928d61)

Bug Fixes

• fix incorrect CJS / ESM distribution (#​17) (048c4ea)

---

Configuration

📅 Schedule: Branch creation - "on Monday every 9 weeks of the year starting on the 5th week" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

[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.

[geotrev]

Unfortunately jest is having a hard time transforming react-merge-refs and is failing about 100 tests due to the issue. I remember we had this problem when trying to upgrade in the past, but couldn't find many conversations about it on slack or GH.

Some things I tried:

• Updating transformIgnorePatterns to include react-merge-refs
• Updating modulePathIgnorePatterns to include react-merge-refs
• Updating tsconfig.json with allowJs: true (thinking it might not be parsing RMF because it's a vanilla JS file).

Unfortunately these didn't seem to crack the code.

[geotrev]

Ah, I see what happepned. Needed to update the file extension whitelist on transform so it would hit mjs. Working now.

[coveralls]

coverage: 96.235%. remained the same
when pulling 71f3860 on renovate/react-merge-refs-2.x
into 7a6734d on main.