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-react-ref

v1.1.0

Published

ESLint plugin to help prevent mistakes when using React's useRef hook.

Downloads

7

Readme

eslint-plugin-react-ref

An ESLint plugin to help prevent mistakes when using React's useRef hook.

Installation

Install ESLint and this plugin:

npm install --save-dev eslint eslint-plugin-react-ref

Usage

Flat Config (eslint.config.js|ts)

Import pluginReactRef and add pluginReactRef.configs.recommended to the extends array of your configuration file:

import { defineConfig } from "eslint/config";
import pluginReactRef from "eslint-plugin-react-ref";

export default defineConfig([
	{
		extends: [pluginReactRef.configs.recommended],
	},
]);

Or, import pluginReactRef and add "react-ref": pluginReactRef to the plugins object of your configuration file, then configure the rule:

import { defineConfig } from "eslint/config";
import pluginReactRef from "eslint-plugin-react-ref";

export default defineConfig([
	{
		plugins: {
			"react-ref": pluginReactRef,
		},
		rules: {
			"react-ref/ref-usage": "warn",
		},
	},
]);

Legacy Config (.eslintrc)

Add plugin:react-ref/recommended-legacy to the extends array of your .eslintrc configuration file:

{
	"extends": ["plugin:react-ref/recommended-legacy"]
}

Or, add react-ref to the plugins array of your .eslintrc configuration file, then configure the rule:

{
	"plugins": ["react-ref"],
	"rules": {
		"react-ref/ref-usage": "warn"
	}
}

Rule

ref-usage

This rule helps enforce proper usage of React's useRef hook by checking two common mistake patterns:

1. Incorrect reference access

Warns when a ref is being accessed directly, instead of with its current property.

Incorrect usage

const ref = useRef(false);

useEffect(() => {
	// `.current` is missing, the test is always truthy,
	// TypeScript doesn't detect anything wrong
	if (ref) {
		// do something
	} else {
		// do something else
	}
// ...

Correct usage

const ref = useRef(false);

useEffect(() => {
	if (ref.current) {
		// do something
	} else {
		// do something else
	}
// ...

Note: in this particular case, the ESLint plugin typescript-eslint and its rule no-unnecessary-condition (part of the strict config) would also detect the incorrect usage, as ref is always truthy.

2. Incorrect value access during render

Warns when a ref's value is being accessed during render.

❌ Incorrect usage

function Component() {
	const ref = useRef(null);

	// Accessing `ref.current` during render
	return <div>{ref.current}</div>;
}

Note that this rule is not yet capable of catching all the possible ways of accessing a ref's value during render. (You could create a function returning a ref's value, and call this function during render; but this is still a React No No!)

Further readings

Read more about useRef and its common pitfalls at react.dev/reference/react/useRef.