Juho Vepsäläinen

Yeah, the plugin has to be **after** `ExtractTextPlugin`. I'll check the repo. Thanks.

Yup, confirmed. The build could stall if it never gets to the callback at https://github.com/webpack-contrib/purifycss-webpack/blob/3b04e3180a6b776e801708e3e608c38a09a3d6b0/src/index.js#L80 . I don't understand how that's possible, though. I guess the next step would be...

Here, https://github.com/webpack-contrib/purifycss-webpack/compare/v0.4.0...v0.5.0#diff-1fdf421c05c1140f6d71444ea2b27638 . It does a lookup little differently.

Are you using the Git version? I haven't published it to npm yet (problems with npm, I have to rename the package etc.). Can you set up a standalone example?

The GitHub version has some serious improvements in it. The API is completely different than in the npm one, though. Your code will fail if you run it against the...

@crvst No probs. I'll rename this plugin today and do some maintenance. Time to get a version out there.

Hi, I published the [new version](https://www.npmjs.com/package/purifycss-webpack). Please adapt your setup to that and see if that helps. I added `verbose` flag that should help in debugging.

If you can set up a small repository showcasing the issue, I don't mind digging into it. Can you see why/where [css package](https://www.npmjs.com/package/css) is used? I haven't seen that on...

`npm ls` I think.

One option is that you have something like `loaders: ['css', ...]` somewhere in your configuration. That will pick up `css` over `css-loader` if you have both installed. I would rewrite...