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

find-unused-css

v0.8.1

Published

Find unused css selectors in your project

Downloads

19

Readme

find-unused-css

Build Status Coverage Status NPM version Node

A npm tool to find unused css selectors in your project.

Installation

npm install find-unused-css -g

Usage

Once the module has been installed, you can run it with this command globally:

find-unused-css

From config file:

Create a config file namely "findUnusedCss.json" with following options:

{
   // paths of css files for analyzing
  "cssFiles": ["./dist/css/*.css"],
  // path of source codes such as html or js files
  "source_files": ["./pages/**/*.html", "./app/**/*.js"],
  // optins for analyzing
  "options" : {
    "htmlAnalyzing": true|false, // default true
    "tplAnalyzing": true|false, // default false
    "reactAnalyzing": true|false, // default false
    "jQueryAnalyzing": true|false // default false
  },
  // list of folders, which are excluded during analyzing
  "excludes": ["./node_modules"]
}

From the command line:

After running find-unused-css you will get two questions from command line

  1. Path of your css file:

Enter a target css file e.g ./css/**/*.css

  1. Path of your html directory

Enter a path of html directory which you would like to scan for unused css selectors e.g ./pages/**/*.html.

  1. Enable Html file analzing

Enter 1 for enabling, 0 otherwise.

  1. Enable React analzing

Enter 1 for enabling, 0 otherwise.

  1. Enable jQuery analzing

Enter 1 for enabling, 0 otherwise.

Once you answered these two questions, your css selectors are scanned for given directory.

Currently supported css selectors are class (.class) and id (#id) selectors.

Development

To start run npm start and

For unit testing just run npm test

Issues

Issues can be reported on the issue tracker.

What is next?

  • Improving the output instead of command line
  • Support for attribute selectors
  • Support for AngularJS

I am very happy for every feedback...

Donation

If this project help you reduce time to develop, you can give me a cup of coffee :)

paypal