Juho Vepsäläinen

Ah, I see. It chokes at `purify-css` then. I would need a project to fix this unless you feel like digging in. 👍

Alright. It's weird `verbose: true` doesn't show anything as `purify` is triggered **after** that. But I'll know more once I have some code to study.

As the project isn't funded at the moment, I am not maintaining it actively. That said, I pushed a branch with an initial test under name `fix/193-recursive-match` in case somebody...

Would it be possible for your dev team to send a patch? The project is unfunded right now so I cannot guarantee a fast turnaround on this one.

Ok, cool. In my personal work, I use always the basic merge and solve configurations through composition as it's easy to reason. > On 5. Aug 2021, at 18.20, molly-hayes...

I haven't tried that. How do you generate the html files?

The problem is that the plugin has been designed to operate against files emitted by webpack. I can accept a PR that implements a loader to achieve what you want.

@mehdi-cit It's alright. Let's leave this issue open in case someone wants to tackle it.

PurifyCSS doesn't detect that case based on static analysis alone. Since you are using CSS Modules, it takes some extra configuration as [discussed in the readme](https://github.com/webpack-contrib/purifycss-webpack#usage-with-css-modules).

Can you set up a standalone project? I can't reproduce this.