Pascal Duez

@ritasousa-farfetch Okay, I'll try to make cssnext update the dependency ;) For the prod env, maybe a `postinstall` script in your `package.json`? ```json "scripts": { "postinstall": "npm i postcss-apply@latest" }...

Hi @enjikaka, what version of `postcss-apply` are you using? The latest `0.8.0` fixes some issues with nested declarations. No warning in console/shell? `postcss-reporter` is nice to have in your pipeline.

It's most likely that `postcss-apply` will be removed from `cssnext`, so I doubt it will be upgraded. You can just override it: `npm i postcss-apply@latest -D`.

@enjikaka You might be interested to know that custom property sets and the `@apply` rule are not in good shape, at the spec level: https://github.com/pascalduez/postcss-apply#web-platform-status

@ZeroCho I don't think there's a new spec reproducing the "mixin" kind of behaviour, the promoted one is now tight to custom elements and the shadow DOM... Crawl those links...

Hi, that seems like a reasonable addition, would you mind providing a quick demo of the use case ? A Codepen or the like. I'll implement it as soon as...

WIP, will try to finish it soonish.

Hi, why not, I can think of real world usages for this. I'm in the (slow) process of re-factoring the code base to tackle #8. So this would happen next.

Hi @jonnitto, yes, it's on my radar, hoping to be able to work on it soon.

Hi, are you sure the `@apply` plugin is executed actually? Because property sets declarations are supposed to be removed from final output. Or most probably it's because the slash is...