Repository navigation
Lint the Vite config files - #2412
Merged
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
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.
Summary
The lint config ignored every
*.config.{js,ts,mjs}file, sovite-plus/prefer-vite-plus-importsnever saw the fourvite.config.tsfiles, which is where a strayviteorvitestimport is most likely to come back.The configs already pass every rule, including the type-aware ones, so nothing else changes.
Evidence
Before: changing
packages/shared/vite.config.tsto import from"vite"passedvp lint.After: the same change fails:
Merge Danger
Door: two-way
Impact: contributors
Lint now covers 4 more files. No runtime or build change.
Related