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

@mdor/eslint-react-config

v0.0.2

Published

Shared ESLint flat configuration with React and React Hooks best practices

Readme

@mdor/eslint-react-config

Shared ESLint flat configuration for React applications. It combines @mdor/eslint-config, @eslint-react/eslint-plugin, and eslint-plugin-react, and eslint-plugin-react-hooks.

Requirements

  • Node.js 22.13 or newer
  • npm 10 or newer
  • ESLint 10.8 or newer within the 10.x release line (^10.8.0)

Installation

npm install --save-dev @mdor/eslint-react-config @mdor/eslint-config eslint typescript

@mdor/eslint-config, ESLint, and TypeScript are peer dependencies because the consuming repository owns their versions. The React plugins and React Hooks plugin are runtime dependencies of this package. npm 7 and newer installs compatible peers automatically; the explicit command above also works with package managers that do not.

If peer dependencies are not installed automatically, install the base preset's plugin peers too:

npm install --save-dev eslint-plugin-regexp eslint-plugin-sonarjs eslint-plugin-unicorn

Usage

// eslint.config.mjs
import eslintReactConfig from "@mdor/eslint-react-config";

export default eslintReactConfig;

The default export includes the base MDOR JavaScript rules, the recommended ESLint React rules, and the latest recommended React Hooks rules. The React and Hooks configurations are also available as the named exports reactConfig and reactHooksConfig for custom composition.

The configuration targets JavaScript and JSX. TypeScript projects should add a TypeScript ESLint parser configuration for TS and TSX files separately.

Use in another repository

For example, a standalone React application can use this structure:

my-react-app/
├── eslint.config.mjs
├── package.json
└── src/
    ├── App.jsx
    └── main.jsx

Add lint scripts to the application's package.json:

{
  "name": "my-react-app",
  "private": true,
  "type": "module",
  "scripts": {
    "lint": "eslint .",
    "lint:fix": "eslint . --fix"
  }
}

Then add the shared preset at the repository root:

// eslint.config.mjs
import mdorReactConfig from "@mdor/eslint-react-config";

export default [
  ...mdorReactConfig,
  {
    files: ["src/**/*.{js,jsx}"],
    rules: {
      "@eslint-react/no-array-index-key": "error",
      "react-hooks/exhaustive-deps": "warn",
    },
  },
];

Run it from that application with:

npm run lint
npm run lint:fix

Test-file overrides

Place exceptions after the shared preset so they take precedence:

// eslint.config.mjs
import mdorReactConfig from "@mdor/eslint-react-config";

export default [
  ...mdorReactConfig,
  {
    files: ["src/**/*.test.{js,jsx}"],
    rules: {
      // custom overrides
    },
  },
];

Compose only the React layers

The default export already contains @mdor/eslint-config. When another repository loads the base preset separately, use the named React entries to avoid applying it twice:

// eslint.config.mjs
import mdorConfig from "@mdor/eslint-config";
import { reactConfig, reactHooksConfig } from "@mdor/eslint-react-config";

export default [
  ...mdorConfig,
  reactConfig,
  reactHooksConfig,
  {
    files: ["src/**/*.{js,jsx}"],
    rules: {
      "react-hooks/set-state-in-effect": "warn",
    },
  },
];

JavaScript and TypeScript in the same repository

This package configures .js, .mjs, .cjs, and .jsx. A repository with TSX files should add its TypeScript parser and rules as separate flat-config entries, then keep this preset for JavaScript and JSX:

// eslint.config.mjs
import mdorReactConfig from "@mdor/eslint-react-config";
import tseslint from "typescript-eslint";

export default [
  ...mdorReactConfig,
  ...tseslint.configs.recommended,
  {
    files: ["src/**/*.{ts,tsx}"],
    languageOptions: {
      parser: tseslint.parser,
    },
  },
];

The TypeScript example additionally requires:

npm install --save-dev typescript-eslint