fix: add vitest import when extending vitest matchers #646
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gnapse
approved these changes
Oct 31, 2024
|
🎉 This PR is included in version 6.6.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
@all-contributors please add @InfiniteXyy for code, bug |
|
I've put up a pull request to add @InfiniteXyy! 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What:
#645
Fix a vitest typing issue when using global mode
Why:
If there is no import of "vitest" in the whole project (for example, vitest is in globalMode), the type merging might not work.
How:
By adding an import of "vitest" when extending the matcher type
reference: https://vitest.dev/guide/extending-matchers.html
Checklist: