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-on-useeffect

v1.1.0

Published

Require a comment before every useEffect call

Downloads

6

Readme

eslint-plugin-comment-on-useeffect

This rule enforces that every useEffect hook in your React components has a comment explaining its purpose. This is particularly useful for maintaining code clarity and understanding the intent behind side effects.

In general, useEffect hooks should follow following rules:

  • single responsibility principle. Do not put multiple unrelated side effects in one useEffect. The comment should explain the purpose of the side effect, just like the name of a function would.
  • changes made in a useEffect should not trigger it again!
  • useRef instead of useState for previous values to avoid unnecessary re-renders

Note: This rule is not intended to enforce comments for every useEffect, but rather to ensure that those that are present are meaningful and informative. This is why useEffect hooks which consist of calls to named functions are ignored, as the function names should be self-explanatory.

Installation

Install the plugin package in your project as:

pnpm add -D eslint-plugin-comment-on-useeffect
npm install -D eslint-plugin-comment-on-useeffect
yarn add -D eslint-plugin-comment-on-useeffect

Usage in Flat config

Add the plugin to your ESLint configuration file:

import eslintPluginCommentOnUseEffect from "eslint-plugin-comment-on-useeffect";
// ... other imports

{
  plugins: {
    "comment-on-useeffect": eslintPluginCommentOnUseEffect,
  },
  rules: {
    "comment-on-useeffect/comment-on-useeffect": "warn",
  },
},

Run from command line

npx eslint src/**/*.{ts,tsx}