feat(eslint): support *.spec.* files for Vitest #14
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
kentcdodds
approved these changes
Oct 24, 2024
Member
kentcdodds
left a comment
kentcdodds
left a comment
There was a problem hiding this comment.
I recommend using *.test.*, but I appreciate the defaults in vitest and we'll just stick with that.
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.
By default, Vitest includes all
.specfiles as well as.testfiles so I've added this to thevitestFilesarray to make sure they're configured correctly too.I've added a "test" to the
fixtureapp and ESLint errors about it not being possible to import from the.specfile in there.