Repository navigation
Bug: variable hoisting ignored in rule "css/no-invalid-properties" #199
Description
Environment
ESLint version: 9.31.0
@eslint/css version: 0.10.0
Node version: 24.4.0
npm version: 11.4.2
Operating System: macOS 15.5 (24F74)
Which language are you using?
stylesheet
What did you do?
Configuration
css/no-invalid-properties: ["error"]
/* eslint css/no-invalid-properties: ["error"] */
.test {
color: var(--myColor);
}
:root {
--myColor: blue;
}What did you expect to happen?
No error as the definition of variable --myColor should be hoisted.
What actually happened?
Can't validate with unknown variable '--myColor'
Link to Minimal Reproducible Example
none
Participation
- I am willing to submit a pull request for this issue.
Additional comments
No response
Reacted by Jeff Rooks
Reacted by Jeff Rooks
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
xbinaryx commentedon Jul 16, 2025
Does
allowUnknownVariables: truework for you?Otlikov commentedon Jul 16, 2025
Option
allowUnknownVariables: trueactually suppressed the error message. Then, however, I don't get any warnings about missing css variables, e.g. if I remove--myColoraltogether.nzakas commentedon Jul 21, 2025
Yeah, we aren't hoisting variables at this point. Once we've implemented eslint/rfcs#136, this will be easy to address.
n8tb1t commentedon Oct 19, 2025
still no solution?
nzakas commentedon Oct 21, 2025
@n8tb1t all updates are posted on the issue.
feat: add CSS custom property tracking to CSSSourceCode
eslint-github-bot commentedon Feb 11, 2026
👋 Hi! This issue is being addressed in pull request #377. Thanks, @wingding12!
feat: add CSS custom property tracking to CSSSourceCode
feat: add CSS custom property tracking to CSSSourceCode and refactor …