feat: add automocking in vitest #666
Merged
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
|
Interesting, thanks for your PR! Changes look good, but do people actually use Vitest in RN apps? |
This package was created to integrate React Native and Vitest, so I am using them together. About the error during CI, this appears to be an error in the integration between Eslint and Prettier. I will fix this. |
When running the lint command, Eslint was displaying an error and not working. This commit fix this by: - Updating dependencies by running `yarn upgrade` - Setting up `eslint-plugin-prettier`
|
Oops! I'll see what went wrong and fix it. |
|
Thank you! |
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.
react-native-mmkvalready has automocking for Jest, but not for Vitest.This commit adds automocking for Vitest test environments just by checking if the
VITEST_WORKER_IDenvironment variable is present.This new functionality was also documented in the README, in the "Testing with Jest or Vitest" section, formerly the "Testing with Jest" section.
This way,
MMKVwill be mocked in both Jest and Vitest test environments.