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-class-scope

v0.0.1

Published

Restrict usage of class/className to specific directories (e.g., components/, ui/).

Readme

eslint-plugin-class-scope

Restrict usage of class / className to specific directories.

Installation

npm install --save-dev eslint-plugin-class-scope

Usage

Add class-scope to your ESLint plugins and configure the rule:

// .eslintrc.js
module.exports = {
  plugins: ["class-scope"],
  rules: {
    "class-scope/only-allow-in": [
      "error",
      { allow: ["components/**", "ui/**"] }
    ]
  }
};

Or use the recommended configuration:

// .eslintrc.js
module.exports = {
  plugins: ["class-scope"],
  extends: ["plugin:class-scope/recommended"]
};

Rule: only-allow-in

This rule enforces that JSX elements cannot use class or className attributes outside of specific directories.

Options

  • allow (array of strings): Glob patterns of directories where class/className is allowed

Examples

Allowed

// components/Button.tsx
<div className="btn btn-primary" />
// ui/Card.tsx
<div className="px-4 py-2 rounded-md bg-blue-600 text-white" />

Error

// pages/Home.tsx
<div className="text-gray-500" />
// ❌ Error: Usage of `class` or `className` is not allowed outside allowed directories: components/**, ui/**

Why?

This plugin helps teams enforce styling layer boundaries. For example:

  • Only allow visual styling in components/ or ui/ directories
  • Prohibit styling in pages/, features/, or business logic layers
  • Maintain clear separation between presentation and business logic

License

MIT