This plugin uses PurifyCSS to remove unused selectors from your CSS. You should use it with the extract-text-webpack-plugin.
Without any CSS file being emitted as an asset, this plugin will do nothing. You can also use the
file plugin to drop a CSS file into your output folder, but it is highly recommended to use the PurifyCSS plugin with the Extract Text plugin.
This plugin replaces earlier purifycss-webpack-plugin and it has a different API!
npm i -D purifycss-webpack purify-css
Configure as follows:
const path = ;const glob = ;const ExtractTextPlugin = ;const PurifyCSSPlugin = ;moduleexports =entry: ...output: ...module:rules:test: /\.css$/loader: ExtractTextPluginplugins:'[name].[contenthash].css'// Make sure this is after ExtractTextPlugin!// Give paths to parse for rules. These should be absolute!paths: glob;
And, that's it! Your scripts and view files will be scanned for classes, and those that are unused will be stripped off your CSS - aka. "purified".
In order to use this plugin to look into multiple paths you will need to:
- npm install --save glob-all
const glob = require('glob-all');at the top of your webpack config
- Then you can pass your paths to an array, like so:
You can pass an object (
<entry> -> [<absolute path>]) to
pathsif you want to control the behavior per entry.
This plugin, unlike the original PurifyCSS plugin, provides special features, such as scanning the dependency files. You can configure using the following fields:
||An array of file extensions for determining used classes within style files. Defaults to
||An array of file extensions for determining used classes within
||Enable CSS minification. Alias to
||An array of absolute paths or a path to traverse. This also accepts an object (
||Pass custom options to PurifyCSS.|
||Set this flag to get verbose output from the plugin. This sets
The plugin does not emit sourcemaps even if you enable
sourceMapoption on loaders!
Usage with CSS Modules
PurifyCSS doesn't support classes that have been namespaced with CSS Modules. However, by adding a static string to
localIdentName, you can effectively whitelist these namespaced classes.
In this example,
purify will be our whitelisted string. Note: Make sure this string doesn't occur in any of your other CSS class names. Keep in mind that whatever you choose will end up in your application at runtime - try to keep it short!
moduleexports =module:rules:test: /\.css$/loader: ExtractTextPluginplugins:...purifyOptions:whitelist: '*purify*';