https://github.com/eslint/css
Perhaps we can expose our rules in more than 1 way? We have our own parser already, so might be worth looking into.
Key differences:
- API for declaring plugins differs:
createPlugin vs POJO with some fields
- API for reporting errors is different
- eslint's AST is CSSTree based, Stylelint uses PostCSS. But actually we prefer CSSTree, so that's good. And that API is very similar to projectwallace/css-parser
https://github.com/eslint/css
Perhaps we can expose our rules in more than 1 way? We have our own parser already, so might be worth looking into.
Key differences:
createPluginvs POJO with some fields