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-comment-slop

v1.2.0

Published

ESLint rules against comment slop: length limits evaluated per logical comment, not per line.

Readme

eslint-plugin-comment-slop

ESLint rules that keep comments short and well-written.

Each rule judges a comment as one logical comment — a run of adjacent // lines, a block comment, or one JSDoc prose section — so a paragraph wrapped across several lines is treated as one unit, never nitpicked line by line.

Installation

Requires ESLint 9+ (flat config) and Node.js 18+.

npm install --save-dev eslint-plugin-comment-slop

Configuration

// eslint.config.js
import commentSlop from 'eslint-plugin-comment-slop'

export default [
  {
    plugins: { 'comment-slop': commentSlop },
    rules: {
      'comment-slop/write-short': ['warn', 120],
      'comment-slop/write-good': 'warn',
    },
  },
]

No preset configurations are shipped at this time.

Rules

| Rule | Description | 💡 | 🔧 | | :------------------------------------------- | :------------------------------------------------------- | :-- | :-- | | write-short | Cap the length of each comment. | | | | write-good | Flag weak prose — passive voice, weasel words, and more. | | | | write-clear | Flag dense, hard-to-read sentences. | | |

Rule documentation is generated from the rule's own test suite, so every documented example is verified behavior.

Development

pnpm install
pnpm test       # vitest, including a docs-sync check
pnpm codegen    # regenerate docs/rules/*.md from the test cases
pnpm build      # dual CJS/ESM build via tsup
pnpm lint       # the plugin lints itself with its own rule

Each rule ships three convention-bound files: src/rules/<name>.ts (implementation, with a markdown JSDoc overview on the exported rule), src/rules/<name>.cases.ts (test cases, which are also the documentation examples), and generated docs/rules/<name>.md. To change rule behavior: update the implementation and cases, then run pnpm codegen — the test suite fails if the generated documentation drifts.

Credits

write-good is a tribute to eslint-plugin-write-good-comments by Dániel Kántor, reworked onto this plugin's logical-comment model. The prose analysis is powered by write-good by Brian Ford.