Actually @ota-meshi maintains https://github.com/ota-meshi/eslint-plugin-css

Oh, didn't realize that :) That plugin seems to be base on a mix of postcss and custom logic, not CSSTree which seems to be where eslint itself is heading :(

I use Stylelint for <style> and style="..." linting so I'm not too interested in @eslint/css, but I wouldn't be opposed to someone adding that feature to this plugin.

Implement SCSS (and other preprocessors) ourselves, since CSSTree explicitly doesn't aim to support them

That's an interesting feature, but it would be better to create something like eslint-plugin-scss first 😄
By the way, Stylelint can also check SCSS if you add a plugin.

1. 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)
2. How do we go about preprocessors?

I don't know much about it, but it might be relevant.
eslint/rfcs#105
eslint/css#65

eslint-plugin-css is intended to check the style defined in a JavaScript object.
However, later @eslint/css was released and the namespace conflicted, so I think the name will be changed in the future 😓

Some people say that the name eslint-plugin-css is misleading because it is a plugin that can check CSS files. However, at the time, ESLint did not have the concept of language plugins, and I thought that ESlint-plugin-CSS meant a plugin that checks CSS defined in JS(ES).

I love eslint-plugin-css by the way.

The users can choose their own preferred namespace anyway.