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-css-modules

v1.2.2

Published

Extended ruleset for stylelint on CSS modules

Downloads

11,979

Readme

stylelint-css-modules

NPM version CircleCI status

Extended ruleset for stylelint on CSS modules

Example usage

  1. Install
npm install stylelint-css-modules --save-dev
  1. Configure
plugins: [
  'stylelint-css-modules',
],
rules: {
  'css-modules/composed-class-names': true,
  'css-modules/css-variables': true,
},
  1. Advanced configuration

The stylelint plugin uses enhanced-resolve to find referenced files. Each rule can configure the resolver with a resolve object. By default, this stylelint plugin is configured with:

{
  resolve: {
    extensions: ['.css'],
  },
}

In order to find SASS files, add an additional extension:

plugins: [
  'stylelint-css-modules',
],
rules: {
  'css-modules/composed-class-names': true,
  'css-modules/css-variables': [true, {
    resolve: {
      extensions: ['.css', '.scss'],
    },
  }],
},

In order to leverage the SASS ~ operator, add an additional module:

plugins: [
  'stylelint-css-modules',
],
rules: {
  'css-modules/composed-class-names': true,
  'css-modules/css-variables': [true, {
    resolve: {
      modules: ['node_modules', 'app/src'],
    },
  }],
},

Contributing

  1. Fork
  2. Install with a variant of Stylelint
  • npm run test9
  • npm run test10
  • npm run test11
  • npm run test12
  • npm run test13
  1. Test: npm test (for running tests without installing Stylelint)
  2. Submit a Pull Request

We are looking for simple and tested code. A green build is a requirement.

Ruleset

css-modules/composed-class-names

Ensures each composed class name exists in the targeted file.

Good

.solo-class {}

.nested-root .intermediary-node .nested-child {}

.chained-root.chained-node.chained-child {}

.lots-of-compositions {
  composes: solo-class;
  composes: nested-root;
  composes: intermediary-node;
  composes: nested-child;
  composes: chained-root;
  composes: chained-node;
  composes: chained-child;
  composes: solo-class nested-child;
  composes: global from global;
  composes: baz from './baz.css';
}

where baz.css:

.baz {}

Bad

.lots-of-compositions {
  composes: does-not-exist;
  composes: does-not-exist from './baz.css';
}

where baz.css

.baz {}

css-modules/css-variables

Ensures each CSS variable is defined locally or in some imported file unless it has a fallback.

Good

@import './baz.css';

:root {
  --some-var: 1;
}

.foo {
  margin: var(--some-var);
  padding: var(--baz-some-var);
  padding: var(--bar-some-var, 10px);
}

where baz.css:

:root {
  --bar-some-var: 1;
}

Bad

.foo {
  margin: var(--some-undefined-var);
  padding: var(--baz-some-var);
}

where baz.css:

:root {
  --bar-some-var: 1;
}