feat: support Vitest mocking #686
Merged
+3,965
−27
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Mocking features cannot be used with Vitest. Attempting to do so would fail as Spectator mocks with Jasmine by default
Issue Number: #679
What is the new behavior?
A new secondary entrypoint
@ngneat/spectator/vitest
has been added, which exports Vitest-compatible mocking methods.Does this PR introduce a breaking change?
Other information
I have tried to add Vitest support the same way Jest support was initially introduced.
I still have to test this on fresh Jasmine, Jest and Vitest setups but so far it looks to be working fine.
This PR does not update the existing schematics.