Update testing-library monorepo (major) #78

Removes the extend-expect script. Users should use
the default import path or one of the new test platform-specific
paths to automatically extend the appropriate "expect" instance.

extend-expect was not documented in the Readme, so this change should
have minimal impact.

Users can now use the following import paths to automatically extend
"expect" for their chosen test platform:

@testing-library/jest-dom - jest (@types/jest)
@testing-library/jest-dom/jest-globals - @jest/globals
@testing-library/jest-dom/vitest - vitest

For example:

import '@testing-library/jest-dom/jest-globals'

Importing from one of the above paths will augment the appropriate
matcher interface for the given test platform, assuming the import
is done in a .ts file that is included in the user's tsconfig.json.

It's also (still) possible to import the matchers directly without
side effects:

import * as matchers from '@testing-library/jest-dom/matchers'

Update kcd-scripts
Drop node < 14

`v5.17.0`

Compare Source

Features

New toHaveAccessibleErrorMessage better implementing the spec, deprecate toHaveErrorMessage (#503) (d717c66)

`v5.16.5`

Compare Source

Bug Fixes

migrate ccs v3 to @adobe/css-tools v4 (#470) (948d90f)

`v5.16.4`

Compare Source

Bug Fixes

Support unenclosed inner text for details elements in to be visible (#396) (af18453)

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

`v16.1.0`

Compare Source

`v16.0.1`

Compare Source

`v16.0.0`

Compare Source

Features

Move @testing-library/dom and @types/react-dom to peer dependencies (#1305) (a4744fa)

BREAKING CHANGES

@testing-library/dom was moved to a peer dependency and needs to be explicitly installed. This reduces the chance of having conflicting versions of @testing-library/dom installed that frequently caused bugs when used with @testing-library/user-event. We will also be able to allow new versions of @testing-library/dom being used without a SemVer major release of @testing-library/react by just widening the peer dependency.
@types/react-dom needs to be installed if you're typechecking files using @testing-library/react.

`v15.0.7`

Compare Source

`v15.0.6`

Compare Source

`v15.0.5`

Compare Source

`v15.0.4`

Compare Source

`v15.0.3`

Compare Source

Bug Fixes

Don't raise TypeScript errors when hydating document (#1304) (067d0c6)

`v15.0.2`

Compare Source

`v15.0.1`

Compare Source

`v15.0.0`

Compare Source

`v14.3.1`

Compare Source

Bug Fixes

Stop using nullish coalescing (#1300) (8434a24)

`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)

Configuration

📅 Schedule: Branch creation - "every weekday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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 was generated by Mend Renovate. View the repository job log.

renovate · 2024-04-16T16:53:54Z

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nielslange/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@">=16.8.0" from @emotion/[email protected]
npm ERR!   node_modules/@emotion/react
npm ERR!     peer @emotion/react@"^11.0.0-rc.0" from @emotion/[email protected]
npm ERR!     node_modules/@emotion/styled
npm ERR!       @emotion/styled@"^11.6.0" from @wordpress/[email protected]
npm ERR!       node_modules/@wordpress/components
npm ERR!         dev @wordpress/components@"19.3.0" from the root project
npm ERR!         1 more (@wordpress/block-editor)
npm ERR!     @emotion/react@"^11.7.1" from @wordpress/[email protected]
npm ERR!     node_modules/@wordpress/components
npm ERR!       dev @wordpress/components@"19.3.0" from the root project
npm ERR!       1 more (@wordpress/block-editor)
npm ERR!   peer react@">=16.8.0" from @emotion/[email protected]
npm ERR!   node_modules/@emotion/styled
npm ERR!     @emotion/styled@"^11.6.0" from @wordpress/[email protected]
npm ERR!     node_modules/@wordpress/components
npm ERR!       dev @wordpress/components@"19.3.0" from the root project
npm ERR!       1 more (@wordpress/block-editor)
npm ERR!   30 more (@react-spring/animated, @react-spring/core, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! dev @testing-library/react@"15.0.7" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^18.0.0" from @testing-library/[email protected]
npm ERR!   node_modules/@testing-library/react
npm ERR!     dev @testing-library/react@"15.0.7" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-05-07T13_33_52_792Z-debug-0.log

renovate · 2024-06-03T15:25:07Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nielslange/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@">=16.8.0" from @emotion/[email protected]
npm ERR!   node_modules/@emotion/react
npm ERR!     peer @emotion/react@"^11.0.0-rc.0" from @emotion/[email protected]
npm ERR!     node_modules/@emotion/styled
npm ERR!       @emotion/styled@"^11.6.0" from @wordpress/[email protected]
npm ERR!       node_modules/@wordpress/components
npm ERR!         dev @wordpress/components@"19.3.0" from the root project
npm ERR!         1 more (@wordpress/block-editor)
npm ERR!     @emotion/react@"^11.7.1" from @wordpress/[email protected]
npm ERR!     node_modules/@wordpress/components
npm ERR!       dev @wordpress/components@"19.3.0" from the root project
npm ERR!       1 more (@wordpress/block-editor)
npm ERR!   peer react@">=16.8.0" from @emotion/[email protected]
npm ERR!   node_modules/@emotion/styled
npm ERR!     @emotion/styled@"^11.6.0" from @wordpress/[email protected]
npm ERR!     node_modules/@wordpress/components
npm ERR!       dev @wordpress/components@"19.3.0" from the root project
npm ERR!       1 more (@wordpress/block-editor)
npm ERR!   30 more (@react-spring/animated, @react-spring/core, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! dev @testing-library/react@"16.1.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^18.0.0 || ^19.0.0" from @testing-library/[email protected]
npm ERR!   node_modules/@testing-library/react
npm ERR!     dev @testing-library/react@"16.1.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-12-05T22_49_05_586Z-debug-0.log

renovate bot force-pushed the renovate/major-testing-library-monorepo branch 3 times, most recently from 5955c91 to 7120723 Compare April 26, 2024 16:05

renovate bot force-pushed the renovate/major-testing-library-monorepo branch 5 times, most recently from 3eacc3e to 5c3ecdf Compare May 7, 2024 13:34

renovate bot force-pushed the renovate/major-testing-library-monorepo branch from 5c3ecdf to d2f0f45 Compare June 3, 2024 15:25

renovate bot force-pushed the renovate/major-testing-library-monorepo branch from d2f0f45 to 831bb52 Compare June 11, 2024 01:05

renovate bot force-pushed the renovate/major-testing-library-monorepo branch 2 times, most recently from 2a54bfd to 3f74c74 Compare July 23, 2024 15:54

renovate bot force-pushed the renovate/major-testing-library-monorepo branch 2 times, most recently from 3595ced to c1c1603 Compare August 29, 2024 11:09

renovate bot force-pushed the renovate/major-testing-library-monorepo branch 2 times, most recently from 9df2e26 to 415972a Compare October 17, 2024 16:54

renovate bot force-pushed the renovate/major-testing-library-monorepo branch from 415972a to 70b03d8 Compare October 31, 2024 17:56

Update testing-library monorepo

5c37bea

renovate bot force-pushed the renovate/major-testing-library-monorepo branch from 70b03d8 to 5c37bea Compare December 5, 2024 22:49

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update testing-library monorepo (major) #78

Update testing-library monorepo (major) #78

renovate bot commented Apr 16, 2024 •

edited

Loading

renovate bot commented Apr 16, 2024 •

edited

Loading

renovate bot commented Jun 3, 2024 •

edited

Loading

Update testing-library monorepo (major) #78

Are you sure you want to change the base?

Update testing-library monorepo (major) #78

Conversation

renovate bot commented Apr 16, 2024 • edited Loading

Release Notes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Features

Bug Fixes

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Bug Fixes

Features

BREAKING CHANGES

Features

Bug Fixes

Bug Fixes

Features

BREAKING CHANGES

Bug Fixes

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Features

Bug Fixes

Features

BREAKING CHANGES

Features

Features

Features

Bug Fixes

Features

Bug Fixes

Features

BREAKING CHANGES

Bug Fixes

Configuration

renovate bot commented Apr 16, 2024 • edited Loading

⚠ Artifact update problem

File name: package-lock.json

renovate bot commented Jun 3, 2024 • edited Loading

⚠️ Artifact update problem

File name: package-lock.json

renovate bot commented Apr 16, 2024 •

edited

Loading

renovate bot commented Apr 16, 2024 •

edited

Loading

renovate bot commented Jun 3, 2024 •

edited

Loading