Update @testing-library/jest-dom 5.17.0 → 6.1.2 (major)

[depfu]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @​testing-library/jest-dom (5.17.0 → 6.1.2) · Repo · Changelog

Release Notes

6.1.2

6.1.2 (2023-08-24)

Bug Fixes

• bump @adobe/css-tools for ESM support (#525) (b959a68)

6.1.1

6.1.1 (2023-08-23)

Bug Fixes

• package.json: update main and module file paths (#523) (853a3e5)

6.1.0

6.1.0 (2023-08-23)

Features

• Publish ESM and CJS (#519)

6.0.1

6.0.1 (2023-08-18)

Bug Fixes

• matchers type is making the global expect unsafe (#513) (bdb34f1)

6.0.0

6.0.0 (2023-08-13)

Features

• local types, supporting jest, @jest/globals, vitest (#511) (4b764b9)

BREAKING CHANGES

• 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

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 6 commits:

• fix: bump @adobe/css-tools for ESM support (#525)
• fix(package.json): update main and module file paths (#523)
• feat: manually trigger release (#520)
• chore: Publish ESM and CJS (#519)
• fix: matchers type is making the global expect unsafe (#513)
• feat: local types, supporting jest, @jest/globals, vitest (#511)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[netlify]

✅ Deploy Preview for firefox-devtools-react-contextmenu ready!

Name	Link
🔨 Latest commit	53abb3c
🔍 Latest deploy log	https://app.netlify.com/sites/firefox-devtools-react-contextmenu/deploys/64ef7d1236299e00081abe11
😎 Deploy Preview	https://deploy-preview-131--firefox-devtools-react-contextmenu.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[julienw]

This looks reasonable and tests are still passing properly!