find-unused-css
v0.8.1
Published
Find unused css selectors in your project
Downloads
22
Maintainers
Readme
find-unused-css
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
- Path of your css file:
Enter a target css file e.g ./css/**/*.css
- 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
.
- Enable Html file analzing
Enter 1 for enabling, 0 otherwise.
- Enable React analzing
Enter 1 for enabling, 0 otherwise.
- 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 :)