Which is Better CSS Purification Tools?
uncss vs purify-css
1 Year
uncsspurify-cssSimilar Packages:
What's CSS Purification Tools?

CSS purification tools are essential in web development for optimizing stylesheets by removing unused CSS rules. This not only reduces the file size of CSS files, leading to faster load times, but also enhances maintainability by keeping the stylesheets clean and relevant to the actual content of the web pages. These tools analyze the HTML content and JavaScript files to determine which CSS selectors are actually used, allowing developers to streamline their stylesheets effectively. By utilizing such tools, developers can improve performance and ensure that their web applications are efficient and responsive.

NPM Package Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
uncss53,4269,415-555 years agoMIT
purify-css33,4779,925-857 years agoMIT
Feature Comparison: uncss vs purify-css

Integration

  • uncss: UnCSS can also be integrated into build tools, but it may require more configuration compared to PurifyCSS. It is particularly effective in environments where HTML is dynamically generated, such as single-page applications.
  • purify-css: PurifyCSS is designed to be easily integrated into various build tools like Gulp, Grunt, and Webpack. It allows developers to customize the process according to their workflow, making it a flexible choice for different project setups.

Performance

  • uncss: UnCSS can sometimes be slower, especially on larger projects, as it analyzes the entire HTML structure to identify unused styles. While it is thorough, this thoroughness can lead to longer processing times compared to PurifyCSS.
  • purify-css: PurifyCSS is known for its performance efficiency, as it focuses on removing only the unused CSS selectors without altering the remaining styles. This results in a smaller CSS file size and improved loading times without compromising the visual integrity of the application.

Configuration Flexibility

  • uncss: UnCSS provides more advanced configuration options, allowing for greater customization in how unused styles are detected and removed. This can be beneficial for experienced developers looking for fine-tuned control over the purification process.
  • purify-css: PurifyCSS offers a simple configuration setup, allowing developers to specify the paths to their HTML and CSS files easily. This simplicity makes it accessible for developers who may not want to dive deep into complex configurations.

Dynamic Content Handling

  • uncss: UnCSS excels in handling dynamic content, as it can analyze the rendered output of JavaScript frameworks. This makes it a better choice for applications where styles are applied conditionally or through client-side scripts.
  • purify-css: PurifyCSS is primarily focused on static content and may not effectively handle styles that are applied dynamically through JavaScript. Developers need to ensure that all relevant HTML is included during the purification process.

Community and Support

  • uncss: UnCSS has a larger community and more extensive documentation, providing a wealth of resources for developers. This can be advantageous for those seeking help or examples on how to effectively use the tool.
  • purify-css: PurifyCSS has a smaller community compared to UnCSS, which may result in fewer resources and examples available for troubleshooting. However, its straightforward nature often leads to fewer issues overall.
How to Choose: uncss vs purify-css
  • uncss: Choose UnCSS if you are looking for a more comprehensive solution that can analyze your HTML files and dynamically generated content. UnCSS is ideal for larger projects where you want to ensure that all unused CSS is removed, including styles that may not be present in static HTML but are generated by JavaScript.
  • purify-css: Choose PurifyCSS if you need a lightweight solution that can be easily integrated into your build process. It is particularly useful for projects where you want to maintain control over the CSS output and prefer a straightforward configuration without additional dependencies.
README for uncss

UnCSS

NPM version Linux Build Status Windows Build status Coverage Status dependencies Status devDependencies Status

UnCSS is a tool that removes unused CSS from your stylesheets. It works across multiple files and supports Javascript-injected CSS.

How

The process by which UnCSS removes the unused rules is as follows:

  1. The HTML files are loaded by jsdom and JavaScript is executed.
  2. All the stylesheets are parsed by PostCSS.
  3. document.querySelector filters out selectors that are not found in the HTML files.
  4. The remaining rules are converted back to CSS.

Please note:

  • UnCSS cannot be run on non-HTML pages, such as templates or PHP files. If you need to run UnCSS against your templates, you should probably generate example HTML pages from your templates, and run uncss on those generated files; or run a live local dev server, and point uncss at that.
  • UnCSS only runs the Javascript that is run on page load. It does not (and cannot) handle Javascript that runs on user interactions like button clicks. You must use the ignore option to preserve classes that are added by Javascript on user interaction.

Installation

npm install -g uncss

Usage

Online Server

Within Node.js

var uncss = require('uncss');

var files   = ['my', 'array', 'of', 'HTML', 'files', 'or', 'http://urls.com'],
    options = {
        banner       : false,
        csspath      : '../public/css/',
        htmlroot     : 'public',
        ignore       : ['#added_at_runtime', /test\-[0-9]+/],
        ignoreSheets : [/fonts.googleapis/],
        inject       : function(window) { window.document.querySelector('html').classList.add('no-csscalc', 'csscalc'); },
        jsdom        : {
            userAgent: 'Mozilla/5.0 (iPhone; CPU iPhone OS 10_3 like Mac OS X)',
        },
        media        : ['(min-width: 700px) handheld and (orientation: landscape)'],
        raw          : 'h1 { color: green }',
        report       : false,
        strictSSL    : true,
        stylesheets  : ['lib/bootstrap/dist/css/bootstrap.css', 'src/public/css/main.css'],
        timeout      : 1000,
        uncssrc      : '.uncssrc',
        userAgent    : 'Mozilla/5.0 (iPhone; CPU iPhone OS 10_3 like Mac OS X)',
    };

uncss(files, options, function (error, output) {
    console.log(output);
});

/* Look Ma, no options! */
uncss(files, function (error, output) {
    console.log(output);
});

/* Specifying raw HTML */
var rawHtml = '...';

uncss(rawHtml, options, function (error, output) {
    console.log(output);
});

At build-time

UnCSS can also be used in conjunction with other JavaScript build systems, such as Grunt, Broccoli or Gulp!

From the command line

Usage: uncss [options] <file or URL, ...>
    e.g. uncss https://getbootstrap.com/docs/3.3/examples/jumbotron/ > stylesheet.css

Options:

  -h, --help                            output usage information
  -V, --version                         output the version number
  -i, --ignore <selector, ...>          Do not remove given selectors
  -m, --media <media_query, ...>        Process additional media queries
  -C, --csspath <path>                  Relative path where the CSS files are located
  -s, --stylesheets <file, ...>         Specify additional stylesheets to process
  -S, --ignoreSheets <selector, ...>    Do not include specified stylesheets
  -r, --raw <string>                    Pass in a raw string of CSS
  -t, --timeout <milliseconds>          Wait for JS evaluation
  -H, --htmlroot <folder>               Absolute paths' root location
  -u, --uncssrc <file>                  Load these options from <file>
  -n, --noBanner                        Disable banner
  -a, --userAgent <string>              Use a custom user agent string
  -I, --inject <file>                   Path to javascript file to be executed before uncss runs
  -o, --output <file>                   Path to write resulting CSS to

Note that you can pass both local file paths (which are processed by glob) and URLs to the program.

  • banner (boolean, default: true): Whether a banner should be prepended before each file block in the processed CSS.

  • csspath (string): Path where the CSS files are related to the HTML files. By default, UnCSS uses the path specified in the <link rel="stylesheet" href="path/to/file.css"/>.

  • htmlroot (string): Where the project root is. Useful for example if you have HTML that references local files with root-relative URLs, i.e. href="/css/style.css".

  • ignore (string[]): provide a list of selectors that should not be removed by UnCSS. For example, styles added by user interaction with the page (hover, click), since those are not detectable by UnCSS yet. Both literal names and regex patterns are recognized. Otherwise, you can add a comment before specific selectors:

    /* uncss:ignore */
    .selector1 {
        /* this rule will be ignored */
    }
    
    .selector2 {
        /* this will NOT be ignored */
    }
    
    /* uncss:ignore start */
    
    /* all rules in here will be ignored */
    
    /* uncss:ignore end */
    
  • ignoreSheets (string[] | RegExp[]): Do not process these stylesheets, e.g. Google fonts. Accepts strings or regex patterns.

  • inject (string / function(window)): Path to a local javascript file which is executed before uncss runs. A function can also be passed directly in.

    Example inject.js file

    'use strict';
    
    module.exports = function(window) {
        window.document.querySelector('html').classList.add('no-csscalc', 'csscalc');
    };
    

    Example of passing inject as a function

    {
      inject: function(window){
        window.document.querySelector('html').classList.add('no-csscalc', 'csscalc');
      }
    }
    
  • jsdom (object) (Supported only by API): Supply the options used to create the JSDOM pages (https://github.com/jsdom/jsdom). At the moment, config.resources is not yet supported.

  • media (string[]): By default UnCSS processes only stylesheets with media query _all_, _screen_, and those without one. Specify here which others to include.

  • raw (string): Give the task a raw string of CSS in addition to the existing stylesheet options; useful in scripting when your CSS hasn't yet been written to disk.

  • report (boolean, default: true): Return the report object in callback.

  • strictSSL (boolean, default: true): Disable SSL verification when retrieving html source

  • stylesheets (string[]): Use these stylesheets instead of those extracted from the HTML files. Prepend paths with the file:// protocol to force use of local stylesheets, otherwise paths will be resolved as a browser would for an anchor tag href on the HTML page.

  • timeout (number): Specify how long to wait for the JS to be loaded.

  • uncssrc (string): Load all options from a JSON file. Regular expressions for the ignore and ignoreSheets options should be wrapped in quotation marks.

    Example uncssrc file:

    {
        "ignore": [
            ".unused",
            "/^#js/"
        ],
        "stylesheets": [
            "css/override.css"
        ]
    }
    
  • userAgent (String, default: 'uncss'): The user agent string that jsdom should send when requesting pages. May be useful when loading markup from services which use user agent based device detection to serve custom markup to mobile devices. Defaults to uncss.

As a PostCSS Plugin

UnCSS can be used as a PostCSS Plugin.

postcss([ require('uncss').postcssPlugin ]);

See PostCSS docs for examples for your environment.

Note: Depending on your environment, you might not be able to use uncss as a PostCSS plugin since the plugin is not directly exported. In such cases, use the wrapper library postcss-uncss.

Options

  • html (string[]): provide a list of html files to parse for selectors and elements. Usage of globs is allowed.

  • ignore (string[] | RegExp[]): provide a list of selectors that should not be removed by UnCSS. For example, styles added by user interaction with the page (hover, click), since those are not detectable by UnCSS yet. Both literal names and regex patterns are recognized. Otherwise, you can add a comment before specific selectors in your CSS:

    /* uncss:ignore */
    .selector1 {
        /* this rule will be ignored */
    }
    
    .selector2 {
        /* this will NOT be ignored */
    }
    
Example Configuration
{
  html: ['index.html', 'about.html', 'team/*.html'],
  ignore: ['.fade']
}

License

Copyright (c) 2019 Giacomo Martino. See the LICENSE file for license rights and limitations (MIT).