`eslint-plugin-react` provides React-specific linting rules for ESLint, helping developers catch common issues and enforce React best practices in JavaScript and JSX code. It includes recommended and other shareable configurations that can be enabled in an ESLint setup.
Project status
- The repo (jsx-eslint/eslint-plugin-react) appears actively maintained, with an upstream push on 2026-05-13, and recent updates as far back as 2025.
- The update cadence looks somewhat irregular from the available data (v7.37.3 in 2024-12, v7.37.4 in 2025-01, v7.37.5 in 2025-04), suggesting periodic maintenance and rule-focused fixes rather than a fixed monthly rhythm.
AI summary generated Today
Recent updates
v7.37.5
4/3/2025v7.37.5 contains several lint-rule fixes related to JSX property validation, prop-types generic support, and improved detection of constructed React context values. The release notes document four rule fixes plus a small docs wording adjustment, but they do not mention any dependency bumps.
v7.37.4
1/12/2025v7.37.4 primarily addresses the eslint-plugin-react rule `no-unknown-property` by adding support for new React/DOM-related attributes, and it includes a TypeScript typing fix for the `flat` config shape. The code diff also shows some additional changes around how the `configs.flat` object is created at runtime, plus a devDependency bump not mentioned in the release notes.
Breakingv7.37.3
12/23/2024v7.37.3 mainly contains targeted bug fixes for rule behavior and TypeScript type declarations. The documented changes include avoiding a crash in `no-danger`, adding React 19 `precedence` support in `no-unknown-property`, and fixing `prop-types` validation when PropTypes are imported via namespace generics.
v7.37.2
10/22/2024v7.37.2 updates the react/destructuring-assignment rule to fix a false negative involving TypeScript `typeof props.a`. The change also refactors the rule internals to use `getParentStatelessComponent`, and the repo contains additional (non-release-noted) configuration and dependency updates.
v7.37.1
10/1/2024v7.37.1 is a small maintenance release focused on distribution/package metadata and a documentation link fix. It includes a change intended to ensure TypeScript declaration files (d.ts) are included correctly in the published npm package, plus a README update to use the latest ESLint shared settings documentation URL.
v7.37.0
9/27/2024v7.37.0 adds TypeScript type generation, and enhances a few rules with pattern-based configuration. Specifically, it adds suggestions (with editor suggestion output and a replacement fix) to `no-unescaped-entities`, introduces `allowedForPatterns` and `disallowedForPatterns` to `forbid-component-props`, and adds a configurable `propNamePattern` (defaulting to `render*`) to `no-unstable-nested-components`.
Featuresv7.36.1
9/12/2024v7.36.1 contains two documented fixes to React-specific lint rules: `no-is-mounted` now has corrected logic when checking the called method name, and `jsx-no-literals` no longer crashes when encountering JSX boolean props without values. The code changes are small but include additional safety checks and test coverage for the updated behavior.
v7.36.0
9/12/2024v7.36.0 adds a new React lint rule (forward-ref-uses-ref) and extends jsx-no-literals with an elementOverrides configuration option. It also includes several robustness fixes across JSX/prop-type related rules (notably using type arguments via propsUtil) and adds the explicitSpread option to jsx-props-no-spreading.
Featuresv7.35.2
9/3/2024v7.35.2 updates the `jsx-curly-brace-presence` rule to prevent an autofix from generating invalid JSX when a string literal contains double quotes. The release notes describe a single targeted fix, and the code diff shows a corresponding change in the rule’s fixer logic for JSX attribute values.
v7.35.1
9/2/2024v7.35.1 is documented as a patch that fixes a false positive in the `jsx-curly-brace-presence` rule, specifically avoiding triggering on strings that contain quote characters. The code diff, however, shows extensive internal changes across many rules, including switching CallExpression checks to a shared `astUtil.isCallExpression` helper and updating TS-related unwrapping logic.