Pascal Duez

@kevinSuttle Is this issue still relevant?

I tried fiddling with the provided repo for an hour or so, I could not get any progress. Looks like the postcss plugins are not even applied/called. By default storybook...

This is concerning enough, even if Webpack 2 is still in beta. Re-opening.

@Memoyr Just a quick remark on what you posted above, `postcss-custom-properties` and `postcss-apply` are already included within `postcss-cssnext`. So apparently you're running them twice. Also the plugins order is important,...

> I have to import the file into my current file anytime I want to use a custom property set. That's how `postcss-import` and most preprocessors works. Only alt solution...

@ericsaboia ~~Basically `postcss-loader` should comes before the `css-loader` so the `apply` plugin should already have done it's job.~~ Edit: I don't know what I'm talking about :) I once tried...

Okay, I spotted the culprit. This happens when used together with CSS modules. It's [`css-selector-tokenizer`](https://github.com/css-modules/css-selector-tokenizer) `stringify` function.

@yebrahim One solution, PR that lib to prevent the escaping. But since custom property sets are not going anywhere, it might be more difficult to get the change accepted, dunno....

Hi, this is because you use nesting, and your `postcss-nested` plugin is one of the last one in the chain. A quick fix would be to move it up. Nonetheless,...

Hi @philipbordallo, thanks a lot for the feedback and research! Obviously I didn't tested it on MacOS, but a couple of days ago I saw the result, and it's looking...