Open
Description
Description
When I implemented CSS parsing, I used PostCSS to do it. Now it seems that eslint itself is steering towards using CSSTree and implements (so far quite limited) CSS linting in @eslint/css
.
I think we should aim to:
- Enable using
@eslint/css
rules in Svelte files - Keep existing
eslint-plugin-svelte
rules working
To that end, we'd need to:
- Migrate everything from PostCSS to CSSTree
- Probably parse the CSS all the time, not just on-demand like we currently do
- Implement SCSS (and other preprocessors) ourselves, since CSSTree explicitly doesn't aim to support them
Open Questions:
- Does Eslint even support multiple languages in one file? Eslint is going the way of multi-language support, but so far it seems like only one language at time is supported (not sure, but see Bug: Cannon use processor and recommended configs together eslint/markdown#353)
- How do we go about preprocessors?
I am willing to do some work on this eventually, but I think some discussion is needed first... Thoughts?