Pascal Duez

Maybe also [postcss-mixins](https://github.com/postcss/postcss-mixins) replicates the kind of Sass like fonctionnality most users are seeking for.

Hi @ai, thanks for the heads up. If I understand correctly the [breakage will happen in PostCSS 8](https://github.com/postcss/postcss/issues/1260#issuecomment-489354967), right?

@japboy I will upgrade it to make it work with PostCSS 8 when available. But actually it's closer to postcss-mixins than postcss-extend in behaviour.

@spnc-omz That "integration" file aims at testing we don't break other CSS features and PostCSS plugins, mainly `postcss-custom-properties`, that's exactly what the test you highlight is for. We should leave...

Hi @tameraydin, I'm not 100% against, although worried by introducing complexity. So if your willing to do so, why not. Important note: did you see the `@apply` rule and custom...

> normally it looks like: `--toolbar-theme:` but with `postcss-nested` it looks like: `:root --test-theme: null`. hi, could you please but a little bit more specific/clear (samples welcome).

All right, still a bit weird, but I'll try to reproduce and see what we can do to make both plugins play together. But the issue looks more on the...

Hi @ritasousa-farfetch, I'll try to run some tests, see what we can do. But there's some crucial points to understand here: `postcss-cssnext` and `postcss-apply` aims at following the standard specs...

@ritasousa-farfetch Okay, I see. Did you try just upgrading the `postcss-apply` plugin in your deps but not running it again after the cssnext one (in plugin list). So basically just...

Also the plugin `postcss-cssnext` is using is [`postcss-nesting`](https://github.com/jonathantneal/postcss-nesting), not `postcss-nested`.