Fix vitest aliases configuration #100
Merged
Conversation
This file contains hidden or 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
| To view this pull requests documentation preview, visit the following URL: react-query-firebase.invertase.dev/~100 Documentation is deployed and generated using docs.page. |
Member Author
Ehesp approved these changes Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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.
Tests currently fail due to vitest failing to resolve the path of
~/testing-util. Vitest seems not to automatically know how to resolve the alias. This PR introduces analiaskey to the vitest config so as to explicitly configure vitest to resolve the path to the alias.