chore: exclude vitest config inside snap tests for VSCode#1723
Merged
Conversation
Signed-off-by: Liang <github@liangmi.dev>
✅ Deploy Preview for viteplus-preview canceled.
|
Contributor
Author
|
The prefix |
fengmk2
approved these changes
May 31, 2026
Member
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
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.
I found that my git usually reports that there is an untracked
.vitest-plugin-loaded, it is generated by a Vitest plugin insidevite-plugins-async-testsnap test and can be removed while running tests. However, Vitest VSCode extension can not run the test but automatically loads the config, which creates this file.This PR adds snap tests directory to Vitest's configure ignore pattern, means Vitest will no longer treat it as a nested config or a workspace project, so this file should not annoy our developing after it.