utils/ts_config/eslint/react.js
Krzysztof kuhy Rudnicki 0f9699d4f3 ts_config: project option, entry-point barrel and className carve-outs
Surfaced by making ts_core and web_ui the first consumers:

- base({ project }) uses an explicit tsconfig list instead of the project
  service. Both packages exclude tests from tsconfig.json so they never land
  in dist/, and widen the include in tsconfig.lint.json for lint only; the
  project service would have reported every test file as "not found".
- unicorn/no-barrel-files is off for src/index.ts: a package entry point IS
  a barrel, that is its job. Stays on everywhere else.
- unicorn/no-keyword-prefix is off in the React layer: `className` is
  React's prop name and fires on every styled element.
- pnpm-workspace.yaml: allowBuilds for unrs-resolver set to false explicitly
  (pnpm 12 had written a placeholder); the resolver's prebuilt binding is
  used, no install script runs.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DnAYyNH1Sm4iJNidfYbrZJ
2026-09-16 21:45:59 +02:00

57 lines
2.0 KiB
JavaScript

// React layer, stacked on base().
//
// Four plugins, each covering ground the others do not:
// - react-hooks: the rules of hooks + exhaustive deps, plus React 19's
// compiler-derived checks (`recommended` in 7.x).
// - @eslint-react: component/JSX correctness, type-checked variant, and the
// replacement for eslint-plugin-react (which crashes under ESLint 10).
// - react-refresh: a file that mixes a component with a non-component
// export silently breaks Vite HMR for the whole module.
// - react-you-might-not-need-an-effect: the article names "an effect that
// derives state from props" as the single most frequent AI edit. The
// fixture's Button does exactly that, and this is the rule that sees it.
// - jsx-a11y: accessibility is "the first thing to go" when a model
// optimises for how the screen looks. Its 6.10.2 peer range stops at
// ESLint ^9, but under 10 it runs cleanly (verified by the fixture test),
// so the `strict` preset is on.
import eslintReact from "@eslint-react/eslint-plugin";
import jsxA11y from "eslint-plugin-jsx-a11y";
import reactHooks from "eslint-plugin-react-hooks";
import reactRefresh from "eslint-plugin-react-refresh";
import youMightNotNeedAnEffect from "eslint-plugin-react-you-might-not-need-an-effect";
import { TS_FILES } from "./base.js";
/** @type {import("eslint").Linter.Config[]} */
export const react = [
{
...eslintReact.configs["recommended-type-checked"],
files: TS_FILES,
},
{
files: TS_FILES,
plugins: { "react-hooks": reactHooks },
rules: reactHooks.configs.recommended.rules,
},
{
files: ["**/*.tsx", "**/*.jsx"],
...jsxA11y.flatConfigs.strict,
},
{
files: TS_FILES,
...youMightNotNeedAnEffect.configs.recommended,
},
{
files: ["**/*.tsx", "**/*.jsx"],
...reactRefresh.configs.vite,
},
{
files: TS_FILES,
rules: {
// `className` is React's own prop name; in a React codebase the rule
// fires on every styled element and cannot be satisfied.
"unicorn/no-keyword-prefix": "off",
},
},
];