adjust vitest ambient declaration file according to vitest docs #612
+7
−3
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:
Changed the way of patching
vitest
types withjest-dom
custom matchersWhy:
The current approach uses
@vitest/expect
module, which is considered to be internal implementation details by thevitest
team according to comments here, so it shouldn't be used to accomplish the goalHow:
New approach follows the latest official
vitest
documentation. There was also docs fix that I proposed and got approved recently, so thevitest
docs website itself isn't reflecting the latest state. To verify that new approach is aligned with docs, you can check this PRAlong the way I removed
export {}
statement since it isn't needed when there areimport
statements are present in the same fileChecklist: