Juho Vepsäläinen

Can you document this a bit? A mention at readme would be enough. I'll merge then.

Yeah, agreed. I would say the right time to update is when they go stable with it. Better leave this open till then.

It's stable now. PR welcome (unless I get to it first).

@freakboy3742 When starting this little venture, my personal goal was to hit $100 income per every day. I'm hitting that goal consistently now. Not every day but very often. In...

Can you provide more information? I get ``` ~/Pr/tm/wm-demo/n/webpack-merge/dist  ls  ✔  16.14.2 Node index.d.ts join-arrays.d.ts merge-with.d.ts types.d.ts unique.d.ts utils.d.ts index.js join-arrays.js merge-with.js types.js unique.js utils.js index.js.map join-arrays.js.map...

Looking at `node_modules\webpack-merge\dist\index.js'` and `dist/index.js`, I wonder if it could it be some path normalization issue. Which versions of Node and npm are you using? Are you on Windows?

@michael-ciniawsky Yeah, it's the same problem for each loader/plugin. We should solve this properly once, push the solution to defaults, and replicate.

It's possible to work around this by [whitelisting](https://github.com/webpack-contrib/purifycss-webpack#usage-with-css-modules) but a completely automatic solution would be better.

The configuration discussed at the readme should be enough. You have to be careful, though, as if you generate class names dynamically, the plugin won't be able to detect them...

My understanding is that purify should pick up `className` but the only way you can say for sure is by actually trying.