Andrey Sitnik

What problem do you have of passing `undefined` to `postcssJs.sync()`? We can throw an error on missed argument.

I am not sure, that we can fix it in `postcss-nested`. The best way is to fix it in `postcss-extend-rule`. We need to migrate it to PostCSS 8.

Nope. We just have not support for multiline at-rules. Do you want to send PR with parenthesis, `\` and semicolon at the end features for at-rules?

Sure. 1. I recommend starting from test. Then with `npx jest -t 'TEST NAME'` you will be able to debug some specific case. 2. Check out what `atrule()` method `parser.js`...

@lifeiscontent I do not plan to create it. You can create. Here is a good guide: https://postcss.org/docs/writing-a-postcss-plugin

@lifeiscontent org doesn’t give a lot of visibility. It is better to mention it in `@Autoprefixer` and `@PostCSS` twitter accounts and add it to https://www.postcss.parts/

> if I'm targeting 116, great majority of the all never versions are supported also It is true only in a majority of the cases, but not for all of...

> is it needed to check the size of the only file/files that have been changed? It is OK to check all

What is the difference?

What `fs.watch` problems do we have?