The more autonomy I give coding agents, the more of a repository's expectations need to be executable.
I do not want manual review to be the first place a predictable failure is discovered.
My projects now have more pre-commit hooks, tests, deterministic checks for project conventions, and small reviewable commits.
The checks turn expectations into pass/fail results an agent can act on; the commits keep failures narrow enough to diagnose.
Linting is one of those guardrails.
This story began when the React linting layer I relied on broke during an ESLint 10 upgrade.
I maintain several React applications and wanted to upgrade them to ESLint
10.
The upgrade stopped at .
ESLint 10 removed deprecated rule-context APIs.
The current release declares support only through ESLint 9 and can crash under ESLint 10 with: The upstream compatibility issue was opened on February 7,
2026.
As of August 23, it is still open more than six months later.
The pull request, opened on July 30, is also still open.
That led me to release : an independent React 19 continuation for ESLint
10.
Who this is for The package has a deliberately narrow support matrix: Tool Supported version React 19+ ESLint 10 Biome 2.5.8+ Node.js 22.13, 24, or 26 ESLint config Flat config React 18, ESLint 9, and are outside the package contract.
My setup My projects use Biome as the primary formatter and linter.
Biome handles general JavaScript, TypeScript, JSX, DOM, and most React checks.
ESLint remains for checks that Biome does not provide, including framework plugins and several React 19 contracts.
The setup came from real Next.js and React codebases behind Albumentations.ai, sportscategory.info, and my-roots.me: Next.js 16 React 19 TypeScript ESLint 10 with flat config Biome with the preset Yarn 4 Node.js 22, 24, and 26 My projects need a smaller rule set: the React-specific checks that still add information after Biome has finished.
What I inherited I started from the upstream repository while preserving its Git history, MIT license, and attribution.
The project is now maintained independently.
At the commit where the fork began, the upstream plugin exported 104 rule modules.
Its preset enabled 102 active rules; the other two were deprecated.
The preset named 22 rules, although one of them, , was explicitly disabled, so it enforced
21.
Carrying all of that forward would have preserved the package size without preserving a clear purpose.
My target was narrower: React 19 checks that still add information after Biome has run.
How 102 active rules became 11 I reviewed the rules by the kind of decision they enforce: Group Decision Same diagnostic already available in Biome Remove from this plugin Formatting, naming, file layout, or team policy Leave to Biome or the application Broad heuristics that need project-wide or type-aware evidence Remove rather than report uncertain results React 18, classic config, parser workarounds, or obsolete React APIs Remove from the React 19 contract React 19 correctness or a useful React-specific performance warning Keep or implement The first group accounted for exactly 20 rules, including , , , and .
The upstream rule support policy records the complete one-to-one mapping to Biome.
Rules such as , , and were removed because they express style or team policy, not React 19 correctness.
Rules such as and were removed because a local AST heuristic cannot reliably answer a project-wide question.
The remaining exclusions were legacy compatibility surface outside the package's stated support matrix.
Four original rule IDs survived that review: , , , and .
What I added Among the upstream proposals relevant to this React 19 cutover, I evaluated three rule ideas that were still unmerged: warn when a component renders ; disallow on function components; prefer lazy initialization.
I initially implemented all three.
I then removed : React 19 permits an return, so forbidding it would be a team convention presented as a framework requirement.
The other two became and .
The first catches an API React 19 ignores; the second is a warning for avoidable render-time work.
I also added or narrowed five rules around concrete React 19 behavior: , , , , and .
That left 11 rules in version 8.0.0.
All 11 are in : nine correctness rules are errors, while the two performance rules are warnings.
A separate preset would either duplicate or differ only by severity, so the package does not expose one.
The corner cases appeared in real projects By , the unit tests and package checks were green.
Then I installed the plugin in Rooted and Albumentations.ai.
That is where the useful failures started.
The first class of failures was HTML attribute metadata. rejected valid attributes such as , , , , , and on , , and .
The fixes arrived in three rounds: issue #21 and PR #22, then issue #25 and PR #26, and finally issue #29 and PR #31.
The final fix separated WHATWG HTML content attributes from React DOM properties instead of treating one metadata source as the whole contract.
The second failure came from Next.js. builds flat config, but it still reads rules from the legacy-shaped field.
My package exposed only , so configuration failed before ESLint could lint a file.
Issue #24 and PR #27 added that read-compatible field without bringing support back into scope.
I also documented the Yarn resolution needed because Next.js imports the plugin under the unscoped name.
Those integrations produced release candidates 4, 5, and
6.
They also changed the test strategy: the final release checks the packed npm archive with , loads it from ESM, CommonJS, and TypeScript consumers, and exercises the supported Next.js configuration shape.
CI covers Node.js 22.13, 24, and
26.
The resulting package uses native ESM, ESLint flat config, and the familiar rule namespace.
How to use it The examples below use Yarn
4.
Install Biome, ESLint 10, and the plugin: Enable Biome's full stable rule set and React domain: Then add the residual React rules to : If the glob includes TypeScript, configure a parser that supports TypeScript earlier in the flat config.
Run both tools: Rule IDs remain under the namespace: Using it with Next.js imports the package under the unscoped name .
With Yarn, map that dependency to the maintained package: Keep both versions synchronized.
This prevents from installing the ESLint 9-only package alongside the ESLint 10 continuation.
Because Next.js registers it under , existing rule IDs continue to work.
When not to use it This package does not cover every rule in the original plugin.
If your configuration depends on rules such as , , or , check the complete rule catalog before migrating.
The package also has no React Native-specific compatibility contract.
DOM rules only analyze proven lowercase HTML elements.
Links GitHub repository npm package v8.0.0 release Rule catalog Upstream rule support policy