feat: add no-unmatchable-selectors rule
#301
Merged
+381
−0
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
nzakas
requested changes
Oct 21, 2025
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.
Prerequisites checklist
What is the purpose of this pull request?
This PR introduces a new rule
no-unmatchable-selectorsto catch CSS selectors that can never match any elements, helping developers identify dead code and potential mistakes in their stylesheets.What changes did you make? (Give an overview)
no-unmatchable-selectorsrule that detects and reports selectors with impossible:nth-*()pseudo-class formulasRelated Issues
#186
This initial implementation focuses on
:nth-*()pseudo-classes, but I plan to expand the rule in follow-up PRs to cover additional scenarios.Is there anything you'd like reviewers to focus on?