David Houweling

I did try and debug it locally today but couldn't work out how to correctly map from the plugin via interpretName and then onward.

Yes I did, sorry i was typing my response from my phone rather than my PC. I'll try and do some research on my end looking into mini-css-extract-plugin as well....

after digging through mini-extract-css-plugin and reading webpack documentation I believe the implementation is quite different (though it's quite difficult to understand given the amount of internal webpack plugins it uses)....

Unfortunately I've had to move on to other work as well but if a bit of time opens up for me i'll look to what I can do to help....

If you're happy to drop `style-loader` support, and given `mini-css-extract-plugin` keeps track of its dependencies and generates the correct source map (I believe), wouldn't it be doable to simply chain...

I believe the solution is simply that the `` under `button.expanded` needs `width: 100%` (of course not the expander). The CSS I used to fix it: ``` scss .button.expanded {...

@rafibomb Yes I am using foundation-emails version 2.1.0. The container doesn't matter. Initially I thought it might, but it doesn't. Put it on its own, put it inside a container,...

In my opinion we should keep the code as clean as possible, so if removing resolves the problem, then great.

Good to see that this is being looked at as I have the similar predicament. Given it is written in node, you could parse the `_settings.scss` file accordingly and apply...

I decided to try using `commitizen` with [option 1 - as a commitizen plugin](https://github.com/leoforfree/cz-customizable#option-1---cz-customizable-as-commitizen-plugin) and its working that way.