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 🙏

© 2025 – Pkg Stats / Ryan Hefner

eslint-plugin-use-effect-require-named-callback

v1.0.0

Published

ESLint rule to require useEffect callbacks to be named functions instead of anonymous functions

Readme

eslint-plugin-use-effect-require-named-callback

An ESLint plugin that requires useEffect callbacks to be named functions instead of anonymous functions, improving code readability and debugging experience.

Installation

pnpm install --save-dev eslint-plugin-use-effect-require-named-callback

Usage

ESLint 9+ (Flat Config)

// eslint.config.js
import useEffectRequireNamedCallback from "eslint-plugin-use-effect-require-named-callback";

export default [
  {
    plugins: {
      "use-effect": useEffectRequireNamedCallback,
    },
    rules: {
      "use-effect/use-effect-require-named-callback": "error",
    },
  },
];

ESLint 8 and below (Legacy Config)

{
  "plugins": ["use-effect-require-named-callback"],
  "rules": {
    "use-effect-require-named-callback/use-effect-require-named-callback": "error"
  }
}

What it does

This rule enforces using named functions as useEffect callbacks instead of anonymous arrow functions or anonymous function expressions.

❌ Incorrect

// Anonymous arrow function
useEffect(() => {
  console.log("component mounted");
});

// Anonymous function expression
useEffect(function () {
  console.log("component mounted");
});

// Async arrow function
useEffect(async () => {
  await fetchData();
});

✅ Correct

// Named function expression
useEffect(function handleMount() {
  console.log("component mounted");
});

// Function declaration passed as variable
function handleMount() {
  console.log("component mounted");
}
useEffect(handleMount);

// Named function with dependencies
useEffect(
  function handleDataUpdate() {
    fetchData();
  },
  [dependency]
);

Why use this rule?

Core Benefits:

  1. Improved debugging experience: Named functions appear clearly in stack traces, making debugging easier
  2. Better code readability: Named functions provide context about what the effect does
  3. Self-documenting code: Function names serve as inline documentation for effect purposes
  4. Consistency: Enforces a consistent pattern across your React application

Debugging Comparison

Without named functions:

Stack trace:
  at <anonymous> (Component.js:15:8)
  at useEffect (react.js:...)

With named functions:

Stack trace:
  at handleDataFetch (Component.js:15:8)
  at useEffect (react.js:...)