npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

postcss-cleaner

v1.2.3

Published

PostCSS plugin to clean unused CSS

Downloads

309

Readme

PostCSS Cleaner

PostCSS plugin to clean unused CSS.


Build Status Dependencies Dependencies Coverage Status

Description

This plugin search for selector presence in your source files, regardless of sources files extension. If it can find a selector, it removes it.

It doesn't create any virtual DOM. Instead, it just read your source files code to check the presence of each selector in each rule.

Usage

let postcss_cleaner = require('postccs-cleaner');

let options = {
    sources: ['array', 'of', 'source', 'files'], // Required, files to compare CSS against
    raw: 'h1.classname test', // Optionnal ,if 'sources' is already included, it will be overwrite
    ignore: ['.ignored-class', /or-ignored-regex/],
    log: {
        sourcesList: false,
        removedRules: false,
        ignoredRules: false
    }
};

postcss([postcss_cleaner(options)]).process(css); // `css` is your stylesheet

Alternatively, you can ignore portions of your CSS using comments.

.foo{ }

/* postcss-cleaner: ignore on*/
.bar{ }
/* postcss-cleaner: ignore off*/

.baz{ }

See PostCSS docs for examples for your environment.

Example

CSS Input

/* Css Input */
.foo {
}

.bar {
}

th td,
tr td {
}

.baz {
}

.js-action {
}

Source files

<!-- HTML Input -->
<div class="foo">
    Lorem ipsum dolor sit amet.
</div>
# Slim Input
table
    tr
        td
            | Lorem ipsum dolor sit amet.
// JS Input
document.querySelector('.js-action').addEventListener('click', e => {
    /* [...] */
});

CSS Output

.foo {
}

tr td {
}

.js-action {
}

To do

  • [x] Improve test suite
  • [ ] Improve doc
  • [ ] Clean plugin's code