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

eslint-plugin-classname-components

v0.0.1

Published

ESLint rules for React components that forbid exposing className on internally styled components.

Readme

eslint-plugin-classname-components

npm version npm downloads

ESLint rules for React components that forbid exposing className on internally styled components, and normalize render-side className expressions toward static literals and variant-driven styling.

The plugin is built for teams that want this contract:

  • styled components should not expose className
  • styled components should not merge prop-driven className into their own render output
  • fully static render-side className values should use plain JSX string literals
  • styling differences should be expressed through meaningful variant props instead

The rules require TypeScript parser services. Configure @typescript-eslint/parser with parserOptions.project.

Note: the npm package/import path stays lowercase as eslint-plugin-classname-components because npm package names cannot contain uppercase letters.

Rules

  • no-classname-prop-in-styled-components Flags component definitions that style themselves internally and still expose a className prop.
  • no-classname-prop-merge-in-styled-components Flags render-side className expressions that merge in prop-driven className values inside internally styled components.
  • prefer-static-classname-in-styled-components Flags render-side className expressions that are fully static and should be written as plain JSX string literals.
  • prefer-plain-props-parameter Flags component parameters that only destructure { ...props } and should be plain props parameters instead.

Configuration

pnpm add -D eslint-plugin-classname-components @typescript-eslint/parser typescript

Add to your eslint.config.js

import typescriptEslintParser from "@typescript-eslint/parser";
import classnameComponentsConfig from "eslint-plugin-classname-components/config";

export default [
  // other settings...
  {
    // set up typescript-eslint
    languageOptions: {
      parser: typescriptEslintParser,
      parserOptions: {
        project: true,
        tsconfigRootDir: import.meta.dirname,
      },
    },
  },
  classnameComponentsConfig({ strict: true }),
];

What Counts As Internal Styling

The rules treat a component as internally styled when it renders className values derived from internal style signals such as:

  • string or template literal class names
  • clsx(...)
  • cn(...)
  • cva(...)
  • local identifiers that resolve to those style expressions
  • merge patterns like clsx("base", className) or cn("base", className)

Pure passthrough alone does not count as internal styling:

  • className={props.className}
  • className={className}
  • {...props} by itself

Recommendations

When a component needs styling choices, prefer variant props such as variant, size, or tone over external className injection.

When a component's final class list is static, prefer className="..." over wrappers such as className={"..."} or className={clsx("...", "....")}.

License

MIT License © 2024-PRESENT Nir Tamir

Thanks

  • https://github.com/antfu/eslint-plugin-antfu for a starter project
  • https://github.com/antfu/eslint-plugin-command for a starter project
  • https://github.com/JoshuaKGoldberg/eslint-plugin-package-json for a starter project