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-suspense-check

v1.0.3

Published

ESLint plugin to enforce naming conventions for React Suspense safety

Readme

한국어 가이드 링크

🧐 Why is this necessary?

React Suspense is powerful, but failing to wrap a component that is loading data in a parent <Suspense> boundary can cause the entire app to freeze or result in a white screen.

ESLint cannot verify if a <Suspense> boundary exists in the parent tree across different files. Therefore, this plugin enforces naming conventions to help developers recognize potential mistakes.

Hook: Hooks that trigger Suspense (throw a Promise) internally must start with useSuspense....

Component: Components using the above hooks must start with Suspense....

In short, it ensures that just by looking at the component name, you realize, "Ah, I need to wrap this in Suspense when using it!"

📦 Installation

# npm
npm install --save-dev eslint-plugin-react-suspense-check
# pnpm
pnpm add -D eslint-plugin-react-suspense-check
# yarn
yarn add -D eslint-plugin-react-suspense-check

⚙️ Configuration

Add the following to your eslint.config.mjs (or .js) file.

import suspensePlugin from 'eslint-plugin-react-suspense-check';

export default defineConfig([
  // ... other configs
  suspensePlugin.configs.recommended, // Apply recommended config

  //... other configs
]);

or

import suspensePlugin from "eslint-plugin-react-suspense-check";

export default defineConfig([
  // ... other configs

   extends: [
      suspensePlugin.configs.recommended, // Apply recommended config
   ],
 //... other configs
]);

📏 Rules Description

Checks the names of hooks and components that trigger Suspense.

❌ Incorrect Examples

// 1. Hook naming violation
// Triggers Suspense but named like a normal hook
function useUserData() {
  throw promise;
}

// 2. Component naming violation
// Uses a Suspense hook but named like a normal component
function UserProfile() {
  const data = useSuspenseUser(); // <--- ⚠️ Warning: Change component name to 'SuspenseUserProfile'.
  return <div>{data.name}</div>;
}

✅ Correct Examples

// 1. Hook name starts with 'useSuspense'
function useSuspenseUserData() {
  throw promise;
}

// 2. Component name starts with 'Suspense'
// The caller can tell just by the name that <Suspense> is required.
function SuspenseUserProfile() {
  const data = useSuspenseUserData();
  return <div>{data.name}</div>;
}