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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@codelaw/rules-css-modules

v0.4.3

Published

codelaw's rules for CSS Modules: the join between *.module.css and the JavaScript that reads styles.x; npm only (SR-RULE-PACKS)

Readme

@codelaw/rules-css-modules

codelaw's rules for CSS Modules — one of the first-party rule packs (SR-RULE-PACKS), on npm only: CSS Modules are a JavaScript bundler feature. The rules read the join between a module stylesheet (*.module.css, *.module.scss, or what [css] modules names) and the JavaScript or TypeScript that imports it.

# codelaw.toml
extends = ["codelaw:css/recommended", "codelaw:css-modules/recommended"]
preview = true   # every rule is `preview` until a corpus run promotes it

[css]
modules = ["src/**/*.styles.css"]    # besides *.module.css and *.module.scss
modules_convention = "camelCase"     # css-loader's localsConvention: how `.btn-primary` is read

The css pack's rules also run on module stylesheets and know :global, :local, composes:, :export {}, :import() {} and @value.

Presets

| preset | rules | ported from | |---|---|---| | css-modules/recommended | 3 | eslint-plugin-css-modules's no-unused-class and no-undef-class, and composes resolution | | css-modules/strict | 5 | the additions to css-modules/recommended (it extends it): names readable as styles.x, no :global |

Rules

| rule | fix | flags | |---|---|---| | css-modules/class-naming | manual | a class styles.x cannot reach without brackets (camelCase, kebab or any) | | css-modules/composes-valid | manual | composes naming a missing file or class, or in a nested or non-class rule | | css-modules/no-global | manual | a :global selector in a module | | css-modules/no-undefined-class | manual | styles.x where the module defines no .x, reported in the JS or TS file | | css-modules/no-unused-class | suggest | a class no file reads |

Dynamic access

styles[name], styles[`btn-${size}`], { ...rest } = styles and passing styles to a function mark the module as read by names the rules cannot see: no-unused-class reports nothing for it. A module no file imports is left alone too. Never a false positive.