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

stylelint-find-rules

v2.2.0

Published

Find stylelint rules that you don't have in your config

Downloads

174

Readme

stylelint-find-rules

Build Status version MIT License codebeat badge PRs Welcome styled with prettier

Find stylelint rules that are not configured in your stylelint config.

Inspired by eslint-find-rules

Example Output

Example

Installation

Install as a dev dependency of your project:

yarn add -D stylelint-find-rules

Or with npm

npm i -D stylelint-find-rules

Usage

This package requires stylelint to be already installed in the project, as it will search for available rules from that package.

npm script

{
  ...
  "scripts": {
    "stylelint-find-unused-rules": "stylelint-find-rules"
  }
  ...
}

Command line

Using npx:

npx stylelint-find-rules

Or the old way:

./node_modules/.bin/stylelint-find-rules

Options

stylelint-find-rules [options]

General:
  -h, --help  Show help                                                                    [boolean]
  --config    Optional, path to a custom config file (passed to cosmiconfig)

Options:
  --version         Show version number                                                    [boolean]
  -u, --unused      Find available rules that are not configured
                    To disable, set to false or use --no-u                 [boolean] [default: true]
  -d, --deprecated  Find deprecated configured rules
                    To disable, set to false or use --no-d                 [boolean] [default: true]
  -i, --invalid     Find configured rules that are no longer available
                    To disable, set to false or use --no-i                 [boolean] [default: true]
  -c, --current     Find all currently configured rules                                    [boolean]
  -a, --available   Find all available stylelint rules                                     [boolean]

Examples:
  stylelint-find-rules
  stylelint-find-rules --no-d --no-i
  stylelint-find-rules --config path/to/custom.config.js

Supported configs

Just like stylelint, this package uses cosmiconfig to find your config data, so if stylelint works for you, this should too.

Custom config file

./node_modules/.bin/stylelint-find-rules --config my-custom-config.js

How does it handle extends?

The rules of extends are added to the list of configured rules, thus, if a rule is covered in an extend config, it will not show up in the unused results.

Contributing

See the CONTRIBUTING document.