Andrey Sitnik

In 6.0 `postcss-plugin` will be very small, just one file for 10 lines of code. But it will also fix first problem and have old API. @yoshuawuyts Why you do...

The best place to solve it is `postcss-load-config`. It should memorize config for minute or so. Sorry, moving config to the core will not fix the problem. Anyway we will...

> it's really only needed to "cache" / require the config once and then just pass that onto postcss for all subsequent calls. It could be too tricky in some...

Seems like we have too dymanic require somewhere. I think client side use case is important. PostCSS and Autoprefixer both support it.

I think we can have internal API for client-side and auto-load API for CLI: ```js // Client-side let core = require('stylelint/…') let scss = require('postcss-scss') core.check(source, { parser: scss })...

I will promote this issue in PostCSS twitter too.

We may need option to change safe gamut: `srgb` (default), `p3`, `rec2020`. Note, that this rule not about feature support. Even when all browsers will support `lch()` and P3 colors,...

> If we use this package, we should send a PR upstream to use files: [] is the package.json as it's heavy. https://github.com/LeaVerou/color.js/pull/126

We can also use @omgovich `colord` when they will add [OKLab support](https://github.com/omgovich/colord/issues/87). `colord` is much [smaller](https://packagephobia.com/result?p=colord) than `color.js`.

@hinok `postcss-scss` handles interpolation in selector. That issue is about much more complex cases (string in interpolation in string). Also, that issue should throw a syntax error. Here is a...