-
-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🔥 Drop dependency @testing-library/jest-dom #4136
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 8d5ef84:
|
61bfb5b
to
77a6f6d
Compare
77a6f6d
to
236e42f
Compare
Edited/Blocked NotificationRenovate 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. |
Codecov Report
@@ Coverage Diff @@
## main #4136 +/- ##
=======================================
Coverage 94.65% 94.65%
=======================================
Files 211 211
Lines 5917 5917
Branches 1358 1358
=======================================
Hits 5601 5601
Misses 300 300
Partials 16 16
Flags with carried forward coverage won't be shown. Click here to find out more. |
This PR contains the following updates:
^5.17.0
->^6.1.2
Release Notes
testing-library/jest-dom (@testing-library/jest-dom)
v6.1.2
Compare Source
Bug Fixes
v6.1.1
Compare Source
Bug Fixes
v6.1.0
Compare Source
Features
v6.0.1
Compare Source
Bug Fixes
v6.0.0
Compare Source
Features
BREAKING CHANGES
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:
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'
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
This PR has been generated by Mend Renovate. View repository job log here.