@zalando/gulp-check-unused-css
v2.1.3
Published
Checks your CSS for unused classes in HTML templates
Downloads
7
Readme
gulp-check-unused-css
Check if all your defined CSS classes are used in your HTML files and vice versa.
Deprecation warning
I didn’t expect this plugin to be considered useful by this many people. To make it useful to even more I made it more extensible. Since this meant a breaking API change anyways, this plugin is now deprecated (i.e. I won’t actively develop it further). Please consider switching to symdiff, the new and better gulp-check-unused-css, for your next project.
WAT?
Consider this picture:
Figure a) represents what you have now. Some classes are defined in your CSS, but never used in the templates. Some classes used in the templates don't appear in your CSS.
Figure b) represents what you actually want. Keeping your CSS and HTML clean improves maintainability of your code. Also you do not send useless bytes to your users, which makes your site loading (slightly, but still) faster.
gulp-check-unused-css
, even though the name is misleading now, will check for the not overlapping parts of figure a) and throw an error if it encounters them.
Installation
npm install --save-dev gulp-check-unused-css
Upgrading
In case you are upgrading from 0.0.x
you should really, REALLY read the docs again. Things that changed:
- How you put HTML files in the plugin
- What this plugin actually checks
- When the plugin throws errors
- How to prevent those errors from breaking your build
- Inverted meaning of
angular
option (now off by default)
So basically everything that's important has changed since. I didn't publish the two 1.x.y
versions, so no worries there.
Usage
Simple use:
var checkCSS = require( 'gulp-check-unused-css' );
gulp
.src([ 'styles/*.css', 'templates/*.html' ])
.pipe( checkCSS() );
For advanced use with gulp-watch
check out the Gulpfile.
The plugin will emit all files you put in (because it has to read all of them before checking), but occasionally break your pipe. This is good for automated build processes, e.g. in CI systems like Jenkins or Travis.
Options
ignore
: Array containing strings and/or regexes, if an unused class matches one of it, it is ignored.globals
: Array of strings identifying predefined sets of ignored classes.angular
: Boolean, passingtrue
will turn the support forng-class
on.
Ignoring classes
This plugin is inspired by the workflow at Github, where a build fails if the classes used in the CSS and the templates do not overlap exactly. However, most of us do not write 100 % of the CSS ourselves but rely on frameworks such as Bootstrap. That's why there are some options available to ignore "global" or "vendor" classes.
You can provide a list of class names or regular expressions that should be ignored.
gulp
.src( 'app.*' )
.pipe( checkCSS({
ignore: [ 'special-js-class', /^vendor-/ ]
}));
Since 1.1.0 you can also add globals: [ '{framework}@{version}' ]
to your options.
gulp
.src( 'app.*' )
.pipe( checkCSS({
globals: [ '[email protected]' ]
}));
And since 2.1.1 it is also possible to add your own globals. Since a "global" is only an array of strings or regexes, you can do it like this:
gulp
.src( 'app.*' )
.pipe( checkCSS({
globals: [ [ 'ignore', /^custom-/ ] ]
}));
Or you define a module that exports this array and require it:
// custom-global.js
module.exports = [ 'ignore', /^custom-/ ];
// Gulpfile
gulp
.src( 'app.*' )
.pipe( checkCSS({
globals: [ require( './custom-global' ) ]
}));
This way you could also automatically create your custom global.
Globals that work out of the box
- Bootstrap 3.2.0 (
[email protected]
)
Development
git clone gulp-check-unused-css
cd gulp-check-unused-css
npm install
# hack hack hack
npm test
Add a global to the project's source
- Fork the project
- Acquire CSS file
cd gulp-check-unused-css
node util/extract.js --file { path to CSS file }
- Now there is a
.ignore
file (which is actually a CommonJS module) next to the file - Rename it appropriately to
{framework}@{version}.js
- Save it to
src/global
- Commit and submit a Pull Request
Changelog
2.1.1
: Support for custom globals2.0.1
: Fix main file for npm2.0.0
: Check HTML files, other breaking changes. See Upgrading1.1.0
: Add support for frameworks1.0.0
: JoinignoreClassNames
andignoreClassPatterns
toignore
0.0.8
: Add support for AngularJS syntax0.0.7
: I don't remember0.0.6
: Add check for empty or invalid CSS files0.0.5
: Fix bug where media queries in the CSS broke everything0.0.4
: Fix bug where those options could not be used together0.0.3
: IntroduceignoreClassNames
,ignoreClassPatterns