Change Request: Allow configurable CSS features

[nzakas]

Environment

ESLint version:
@eslint/css version:
Node version:
npm version:
Operating System:

What problem do you want to solve?

The CSS plugin currently only validates known at-rules, properties, values, etc. For libraries like Tailwind that define custom syntax, that means the rules in this plugin flag everything as an error. There are probably other tools that have similar issues.

What do you think is the correct solution?

Create languageOptions for the CSS language that allow the addition of custom at-rules, properties, functions, etc.

These should then be picked up by the parser and lexer so that validation is consistent across all ESLint rules.

Participation

• I am willing to submit a pull request for this change.

Additional comments

Related:

• Rule Change: Allow for configurable properties #36
• Rule Change: Allow for configurable at rules #35