feat: introduce new @jest/expect-utils
package
#12323
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #11867.
We also need to figure out how to expose
build/matchers
, but that also ties into adding custom TS matchers. Not 100% sure how to deal with that?Also, far from all utils need to be exposed in this way, we should cull the API surface.
EDIT: Hmm, would it be better to just add all this to
jest-matcher-utils
?Test plan
Green CI