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-only

v1.0.1

Published

Run stylelint with only one or more specific rules using your current config. It's kind of like [eslint-nibble](https://www.npmjs.com/package/eslint-nibble) for stylelint!

Downloads

55

Readme

stylelint-only

Run stylelint with only one or more specific rules using your current config. It's kind of like eslint-nibble for stylelint!

Install

npm install --dev stylelint-only

Usage

npx stylelint-only [rules] -- [files] [stylelint arguments]

The stylelint-only CLI writes a JSON configuration to disk with all but the specified rules disabled, then runs the stylelint CLI with that configuration and the rest of the provided arguments. For instance, to autofix only a single rule in your src directory:

npx stylelint-only color-hex-case -- --fix src

Options

The following options are respected (before the -- in the CLI arguments, after which all arguments are passed to stylelint):

  • -o path writes the generated configuration to the provided path.
  • --files path tells stylelint's printConfig() function the file for which it should resolve the configuration. The default is . (the current working directory). Despite the plural name, this option should be a single path and may not contain any globs or other "magic" characters.

Gotchas

It's very possible that the generated configuration will not respect nested stylelint configuration overrides. If your project relies heavily on nested configurations, you should pass the --files option to tell stylelint-only the first path from which to generate the temporary config file, as in:

npx stylelint-only color-hex-case --files path/to/file.css -- --fix path/to/file.css