Update dependency @testing-library/react to v14 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@testing-library/react	12.0.0 -> 14.3.0

---

Release Notes

testing-library/react-testing-library (@​testing-library/react)

v14.3.0

Compare Source

v14.2.2

Compare Source

v14.2.1

Compare Source

Bug Fixes

• Update types to support all possible react component return values (#​1272) (55e79c2)

v14.2.0

Compare Source

Features

• add reactStrictMode option to enable strict mode render (#​1241) (0880eba)

v14.1.2

Compare Source

Bug Fixes

• revert missing hooks warnings (#​1255) (1c67477)

v14.1.1

Compare Source

Bug Fixes

• log globals warning only once (#​1252) (fd52a59), closes #​1249

v14.1.0

Compare Source

Features

• add warnings when globals are missing (#​1244) (d80319f)

v14.0.0

Compare Source

Bug Fixes

• Prevent "missing act" warning for queued microtasks (#​1137) (f78839b)

Features

• Bump @testing-library/dom to 9.0.0 (#​1177) (6653c23)
• Drop support for Node.js 12.x (#​1169) (9b7a1e2)

BREAKING CHANGES

• See https://github.com/testing-library/dom-testing-library/releases/tag/v9.0.0
• Minimum supported Node.js version is now 14.x

v13.4.0

Compare Source

Features

• renderHook: allow passing of all render options to renderHook (#​1118) (27a9584)

v13.3.0

Compare Source

Features

• Use globalThis if available (#​1070) (c80809a)

v13.2.0

Compare Source

Features

• Export RenderHookOptions type (#​1062) (46b28ad)

v13.1.1

Compare Source

Bug Fixes

• TS: export interface RenderHookResult (#​1049) (9171163)

v13.1.0

Compare Source

Features

• Add renderHook (#​991) (9535eff)

v13.0.1

Compare Source

Bug Fixes

• Specify a non-* version for @​types/react-dom (#​1040) (2a889e8)

v13.0.0

Compare Source

Features

• Add support for React 18 (#​1031) (ccd8a0d)

BREAKING CHANGES

• Drop support for React 17 and earlier. We'll use the new createRoot API by default which comes with a set of changes while also enabling support for concurrent features.
  To opt-out of this change you can use render(ui, { legacyRoot: true } ). But be aware that the legacy root API is deprecated in React 18 and its usage will trigger console warnings.

v12.1.5

Compare Source

Bug Fixes

• Only supports React < 18 (#​1041) (9e2b5db)

v12.1.4

Compare Source

Bug Fixes

• Match runtime type of baseElement in TypeScript types (#​1023) (96ed8da)

v12.1.3

Compare Source

Bug Fixes

• Add @types/react-dom as a direct dependency (#​1001) (149d9a9)

v12.1.2

Compare Source

Bug Fixes

• render: Don't reject wrapper types based on statics (#​973) (7f53b56)

v12.1.1

Compare Source

Bug Fixes

• TS: make wrapper allow a simple function comp (#​966) (cde904c)

v12.1.0

Compare Source

Features

• improve JSDocs for RenderOptions (#​909) (fbacb0d)

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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.

[jmaher]

@beatrice-acasandrei @alexandru-io can one of you work on this- it is failing on perfherder tests

[Archaeopteryx]

This depends on the React upgrade in #7672

[jmaher]

@alexandru-io this also has been 6 months with no action.

[alexandru-io]

Sorry @jmaher we'll look into it with higher priority.
cc @beatrice-acasandrei

[esanuandra]

Hey @jmaher, I looked into the releases for testing-library/react. For this upgrade to testing-library/react v14 we need React 18 on Perfherder (current version is React 17). Starting from testing-library/react v13 they have dropped support for React 17 and earlier.

testing-library/react v12 only supports React < 18.

Do we plan to upgrade to React 18?

[jmaher]

yes that is the goal, see #7798 ; we keep running into failing perf tests on a lot of things (see the comments).

it appears there is nothing to do with this right now.