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

@geniemouse/stylelint-config

v1.0.3

Published

Shared stylelint configuration settings

Downloads

12

Readme

@geniemouse/stylelint-config

Keep project CSS formatting consistent and free of obvious errors across projects with stylelint and this base configuration.

This configuration is strict.

  1. Installation
  2. Configuration
    1. package.json
    2. .stylelintrc
    3. Adding new/overriding rules
    4. Using alongside Prettier

Installation

  1. Install stylelint locally:
# Using npm:
npm install stylelint --save-dev

# Using yarn:
yarn add stylelint --dev
  1. Install the GenieMouse stylelint configuration package locally:
# Using npm:
npm install @geniemouse/stylelint-config --save-dev

# Using yarn:
yarn add @geniemouse/stylelint-config --dev

Configuration

Add the stylelint set-up instructions to either the package.json or a .stylelintrc file in your project's root directory.

package.json

"stylelint": {
    "extends": ["@geniemouse/stylelint-config"]
    "rules": {
        // Add new/overriding rules, as necessary
    }
}

.stylelintrc

{
    "extends": ["@geniemouse/stylelint-config"],
    "rules": {
        // Add new/overriding rules, as necessary
    }
}

Adding new/overriding rules

Additional stylelint rules/overrides should be written to the rules property.

More information about stylelint's settings can be found on their site:

Using alongside Prettier

If Prettier is being used in your project or editor, some additional node packages will be required to have the two configurations running well together.

# Using npm:
npm install stylelint-prettier stylelint-config-prettier --save-dev

# Using yarn:
yarn add stylelint-prettier stylelint-config-prettier --dev

Add the stylelint-prettier/recommended configuration to the plugins extends array.

E.g. For a .stylelintrc file, it looks like this:

{
    "extends": [
        "@geniemouse/stylelint-config",
        "stylelint-prettier/recommended" // Ensure that stylelint-prettier is called last
    ],
    "rules": {
        // Add new/overriding rules, as necessary
    }
}

Additional project script command

With the installation of stylelint-config-prettier, a new command can be added to the scripts section of your package.json file:

"scripts": {
    // ...
    "stylelint-check": "stylelint-config-prettier-check",
    // ...
}

Running this command will report any conflicting Prettier/stylelint rules.

  • npm run stylelint-check
  • yarn stylelint-check