purifycss-webpack
purifycss-webpack copied to clipboard
UNMAINTAINED, use https://github.com/FullHuman/purgecss-webpack-plugin
Minimal repro project: https://github.com/vitosamson/purifycss-webpack-repro. There are two entry points: `src/split` and `src/not-split`. Both pull in `src/Child`, but `split` does so via `require.ensure` for async code splitting. `Child` imports `react-select`'s css....
### Current Behavior Currently when using `purifycss-webpack` with multi-entry (aka multi-page app) builds, the `paths` option is applied against every `Entrypoint`. In multi-page app builds this can lead to unnecessary...
My webpack.config has the loader purifycss and when use class names in my components react, this doesn't recognize it and clear them. some solution?  
There should be a mechanism that would write the readme table based on the fields and their descriptions. This is likely something that should be tackled in **webpack-defaults** first.
Addition of `webpack-defaults` & associated refactoring as a part of the next `Major` release Issue exists for status tracking across the organization. >Please do not close
Currently Purify loses CSS Modules generated class names as they go through a reference. The Purify plugin should detect the class names somehow and whitelist them to avoid this problem.
I don't know why, but nowadays my webpack don't finish after ~10 mins: ``` 90% recording ``` I don't have too many components and, If I avoid Purify section from...
The plugin ignores css files if they have a hash attached to them. `/css/app.style.css?7ec000f0d0dbcb1dd347` If it was generated like this: ``` new ExtractTextPlugin({ filename: '/css/[name].style.css?[hash]', }), ``` I had customized...
is compatible with the react components and common chunks plug-in. how it should configured with this.
It should be `['css']` always as others don't make sense with Purify.