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-react-hooks-fix-via-todo-comment

v0.0.5

Published

ESLint rules for React Hooks

Readme

eslint-plugin-react-hooks-fix-via-todo-comment

Forked from https://github.com/facebook/react/blob/main/packages/eslint-plugin-react-hooks

How to use this

  1. Assuming you already have ESLint installed, run:
# npm
npm install eslint-plugin-react-hooks-fix-via-todo-comment --save-dev

# yarn
yarn add eslint-plugin-react-hooks-fix-via-todo-comment --dev
  1. Then replace the react-hooks in eslint config to react-hooks-fix-via-todo-comment:
{
  "extends": [
    // ...
---    "plugin:react-hooks/recommended"
+++    "plugin:react-hooks-fix-via-todo-comment/recommended"
  ]
}
  1. Run yarn lint --fix

  2. replace all generated

//eslint-disable-next-line react-hooks-fix-via-todo-comment/exhaustive-deps

to

//eslint-disable-next-line react-hooks/exhaustive-deps

  1. restore your eslint config

  2. uninstall this library.

Advanced Configuration

exhaustive-deps can be configured to validate dependencies of custom Hooks with the additionalHooks option. This option accepts a regex to match the names of custom Hooks that have dependencies.

{
  "rules": {
    // ...
    "react-hooks-fix-via-todo-comment/exhaustive-deps": ["warn", {autoFixComment: "// FIXME(?): it will be fixed by someone else."}]
  }
}

Note

only a very little part of tests are be updated and tested

Questions:

Q: Why doing this?

A: Doing this enables fixing react-hooks/exhaustive-deps warnings gradually when you have time and set the eslint config for react-hooks/exhaustive-deps to error level today.

Q: Why needed to replace react-hooks-fix-via-todo-comment/exhaustive-deps manually?

A: Generating //eslint-disable-next-line react-hooks/exhaustive-deps won't stop in the multi passes of eslint and cause a infinite loop. Looking around the node to stop emit problem is doable but I didn't bother doing so.

Q: Why not codemod?

A: https://github.com/facebook/jscodeshift seems a good candidate but as the origin code is written as an eslint plugin, it's requires minimum modification to achieve the goal.