chore(deps): update devdependency @eslint-react/eslint-plugin to v5

v5.28.8

Compare Source

🐞 Fixes

• react-x/purity: builtin member resolution no longer follows computed or unknown middle segments (ex: window[fetch], window.myLibrary.fetch), preventing false reports of non-builtin calls. (#​2074)

🏗️ Internal

• @eslint-react/eslint: added dual-purpose getText for direct or callback-style source text extraction, replacing repeated context.sourceCode.getText wrappers across packages. (#​2073)

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.28.7...v5.28.8

v5.28.7

Compare Source

🐞 Fixes

• react-x/purity: now reports Date calls during render, including Date(), Date(arg), and window.Date(); unlike new Date(arg), Date(arg) ignores its arguments and always returns the current time. (#​2071) Thanks to @​aki05162525!

🏗️ Internal

• Bumped effect and @effect/platform-node to 4.0.6, @tanstack/react-router to 1.170.46, @tanstack/react-start to 1.169.4, and eslint-plugin-de-morgan to 2.3.0.

New Contributors

• TAKAGI AKIHIRO (@​aki05162525) made their first contribution in #​2071.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.28.6...v5.28.7

v5.28.6

Compare Source

🐞 Fixes

• react-x/set-state-in-effect: the ref-derived parameter exemption now also applies to helpers wrapped in useCallback (ex: measure(ref.current) where measure = useCallback((el) => { setWidth(el.offsetWidth); }, [])). (#​2065) Thanks to @​amhunt!
• react-x/set-state-in-effect: a helper call behind a ref-derived guard (if, ternary, short-circuit, or early return) now exempts the setState calls it reaches, as a setState written in its place would be (ex: if (!anchorRef.current) return; commitPosition(0, true);); call sites are judged individually. (#​2065) Thanks to @​amhunt!

New Contributors

• Andrew Hunt (@​amhunt) made their first contribution in #​2065.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.28.5...v5.28.6

v5.28.5

Compare Source

✨ New

• react-dom/no-unsafe-target-blank: the suggested fix now adds rel="noreferrer" instead of rel="noreferrer noopener", since noreferrer already implies noopener per the HTML spec; values combining both tokens remain valid. (#​2068)

🏗️ Internal

• Removed redundant transitive dependency overrides. (#​2064)
• Bumped vite to 8.3.5 and lucide-react to 1.61.0.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.28.4...v5.28.5

v5.28.4

Compare Source

🐞 Fixes

• Reverted the component-scope-bounded identifier resolution introduced in v5.28.3, including the per-component single-report attribution; class declarations in a component body remain recognized as per-render constructions. (#​2062)

  Affected rules:

  • react-x/no-unstable-context-value
  • react-x/no-unstable-default-props

📝 Documentation

• Updated the AST Explorer links across the website docs and recipes.

🏗️ Internal

• @eslint-react/var: removed the boundary option from resolve and resolveObjectType, and the ClassDeclaration resolution in resolveObjectType, following the revert. (#​2062)
• Renamed the Jsx-prefixed @eslint-react/core exports to all-caps JSX (ex: JsxConfig → JSXConfig, isJsxLike → isJSXLike). (#​2061)
• Bumped fumadocs-mdx to 15.4.9.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.28.3...v5.28.4

v5.28.3

Compare Source

✨ New

• Identifier resolution is now bounded by the enclosing component scope, so render-scoped values referenced from nested callbacks (ex: items.map((item) => <Context.Provider value={foo}>)) are now detected, values declared outside the component (ex: module-level constants) are treated as stable, and nested components report each value only once, attributed to the innermost component. (#​2060)

  Affected rules:

  • react-x/no-unstable-context-value
  • react-x/no-unstable-default-props

• Class declarations (ex: class Foo {} in a component body) are now recognized as per-render constructions, so using one as a context value or default prop is now reported. (#​2060)

  Affected rules:

  • react-x/no-unstable-context-value
  • react-x/no-unstable-default-props

🏗️ Internal

• @eslint-react/var: resolve and resolveObjectType now accept a boundary option that bounds scope-chain traversal to an enclosing component or hook; resolveObjectType also resolves ClassDeclaration nodes. (#​2060)
• Bumped typescript-eslint to 8.72.0, fumadocs-core and fumadocs-ui to 16.17.7, fumadocs-mdx to 15.4.8, lucide-react to 1.60.0, and typedoc-plugin-markdown to 4.14.1.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.28.2...v5.28.3

v5.28.2

Compare Source

🐞 Fixes

• Website: fixed a build failure caused by an unquoted : sequence in the YAML frontmatter description of the react-x/use-memo doc; the rule scaffold script now emits a YAML-safe quoted description so scaffolded rules cannot reintroduce the issue.

📝 Documentation

• Aligned the react-debug/jsx rule doc messages with the actual JSON report format.
• Corrected the documented minimum ESLint version to 10.0.0 in the READMEs and getting-started guides.
• Documented per-layer isolated testing in the fact-based rule implementation patterns guide.
• Generalized the isAPI/isAPICall docs and updated the custom rule samples to use is.APICall. (#​2059)

🏗️ Internal

• Added unit tests for the react-x immutability rule modules (collect, effects, helpers, origins). (#​2056)
• Bumped the postcss override to 8.5.31.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.28.1...v5.28.2

v5.28.1

Compare Source

🐞 Fixes

• react-dom/no-unknown-property: fixed a false positive where the React camelCase SVG prop renderingIntent was reported as an unknown property, including on code produced by this rule's own autofix for rendering-intent. (#​2055)
• react-jsx/no-useless-fragment: the auto-fixer no longer unwraps fragments outside JSX whose children are all whitespace (ex: const x = <> </>; or return <>\n</> with allowExpressions: false); the previous fix produced syntactically invalid JavaScript such as const x = ;. These fragments are still reported, just without a fix. (#​2055)

📝 Documentation

• Aligned rule docs, comments, and diagnostic messages with actual behavior across the plugins. (#​2055)

🏗️ Internal

• Bumped eslint to 10.13.0, pnpm to 12.14.0, tsl-dx to 0.15.0, @effect/language-service to 0.87.5, and lucide-react to 1.59.0.
• Added a TanStack Start example project.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.28.0...v5.28.1

v5.28.0

Compare Source

✨ New

• @eslint-react/eslint-plugin: the general-purpose presets now enable JSX syntax support via languageOptions.parserOptions.ecmaFeatures.jsx: true, so you no longer need to configure it yourself. (#​2049)

  Affected presets:

  • recommended
  • recommended-typescript
  • recommended-type-checked
  • strict
  • strict-typescript
  • strict-type-checked

🏗️ Internal

• Bumped fumadocs-core and fumadocs-ui to 16.17.5, and lucide-react to 1.58.0.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.27.4...v5.28.0

v5.27.4

Compare Source

🐞 Fixes

• @eslint-react/jsx: resolveAttributeValue now handles a parser-tolerated JSXFragment in attribute value position (ex: <a href=<></> />), reporting it as kind "element" instead of falling through to undefined; as a result, react-dom/no-missing-iframe-sandbox now reports <iframe sandbox=<></> /> instead of silently skipping it. (#​2048)

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.27.3...v5.27.4

v5.27.3

Compare Source

🐞 Fixes

• react-jsx/no-key-after-spread: the fast-path text check now matches key assignments with whitespace around = (ex: <div {...props} key = {id} /> or a newline before =), so such elements are no longer silently skipped. (#​2043) Thanks to @​amir-rahmanii!
• react-jsx/no-children-prop: a children prop alongside nested children content (ex: <div children="x">y</div>, createElement("div", { children: "x" }, "y")) is no longer reported by this rule — that conflict case belongs to react-jsx/no-children-prop-with-children — removing the unsafe merge suggestion and the duplicate diagnostics. (#​2044) Thanks to @​amir-rahmanii!
• react-jsx/no-children-prop-with-children: empty expression containers (ex: {}, {/* comment */}) are no longer treated as meaningful children, so <div children="x">{/* comment */}</div> is no longer reported. (#​2045) Thanks to @​amir-rahmanii!

📝 Documentation

• react-naming-convention/ref-name: corrected the additionalRefHooks example to use the /pattern/flags RegExp string form; a bare (a|b) string is treated as exact equality and never matches. (#​2042) Thanks to @​amir-rahmanii!
• The settings docs examples for the additional hooks settings now use full RegExp strings. (#​2047)

🏗️ Internal

• @eslint-react/jsx: hasChildren now treats empty expression containers as non-meaningful, aligned with getChildren. (#​2045)
• react-x: refactored the internals of set-state-in-effect, set-state-in-render, and static-components for readability; no behavior change. (#​2041)
• Bumped vitest to 5.0.5, next to 16.4.2, fumadocs-core and fumadocs-ui to 16.17.4, and undici to 8.12.2.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.27.2...v5.27.3

v5.27.2

Compare Source

🏗️ Internal

• Added the missing @tsconfig/node20 and @types/node dependencies to the workspace packages. (#​2040)
• Bumped effect and @effect/platform-node to 4.0.5, import-integrity-lint to 1.3.1, and sort-package-json to 4.1.0. (#​2040)

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.27.1...v5.27.2

v5.27.1

Compare Source

🐞 Fixes

• Lifecycle methods defined as class properties (ex: componentDidMount = () => { this.setState(...) }, including type-expression-wrapped values) are now reported just like the method shorthand form. (#​2039)

  Affected rules:

  • react-x/no-set-state-in-component-did-mount
  • react-x/no-set-state-in-component-did-update
  • react-x/no-set-state-in-component-will-update

• Effect cleanups are now recognized when the useEffect call is nested in an outer return (ex: return useEffect(() => () => { ... })), so resources released there are no longer reported as leaked. (#​2039)

  Affected rules:

  • react-web-api/no-leaked-event-listener
  • react-web-api/no-leaked-fetch
  • react-web-api/no-leaked-intersection-observer
  • react-web-api/no-leaked-interval
  • react-web-api/no-leaked-resize-observer
  • react-web-api/no-leaked-timeout

🏗️ Internal

• @eslint-react/ast: added the Check.isFunctionOrClass and Check.isTypeOrChainExpression helpers; parent lookups across ast, core, and the rules are now bounded at enclosing function/class boundaries. (#​2039)
• @eslint-react/core: isUseEffectSetupCallback and isUseEffectCleanupCallback reimplemented on bounded parent lookups. (#​2039)

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.27.0...v5.27.1

v5.27.0

🐞 Fixes

• react-web-api/no-leaked-event-listener: cleanups returned through conditional expressions (ex: return cond ? () => window.removeEventListener(...) : null) are now recognized and no longer reported. (#​2038)
• react-web-api/no-leaked-fetch: effect setups wrapped in type expressions (ex: useEffect((() => { fetch(...) }) as any, [])) are now recognized. (#​2038)
• react-debug/function-component: computed string-literal displayName keys (ex: App["displayName"] = "...") are now recognized. (#​2038)

📝 Documentation

• Revised the rule implementation pattern guides and refined the core ideas and layer dependency model in the fact-based rule implementation docs. (#​2034, #​2035)

🏗️ Internal

• @eslint-react/core: accuracy and consistency fixes in detection helpers. (#​2038)
• react-x: the custom tsl config now enforces the fact-based layer dependency order. (#​2036)
• Bumped react and react-dom to 19.3.1, and next to 16.4.1.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.26.7...v5.27.0

v5.26.7

Compare Source

🏗️ Internal

• @eslint-react/core: collectors now use the node's source range start as the map key, replacing the shared counter, keys are stable across repeated lints, traceable to source positions when debugging, and slightly cheaper than stringified numbers. (#​2033)

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.26.6...v5.26.7

v5.26.6

Compare Source

🏗️ Internal

• @eslint-react/core: component and hook collectors now use sequential integer keys instead of random randomBytes hex keys, removing node:crypto from the lint hot path. (#​2032) Thanks to @​kurtextrem!
• Bumped effect to 4.0.4, ts-pattern to 5.9.2, fumadocs-core and fumadocs-ui to 16.17.3, lucide-react to 1.57.0, oxlint to 1.88.0, typedoc-plugin-markdown to 4.14.0, and undici to 8.12.1.

New Contributors

• Jacob Groß (@​kurtextrem) made their first contribution in #​2032.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.26.5...v5.26.6

v5.26.5

Compare Source

🐞 Fixes

• react-x/set-state-in-effect: a setState on the right side of a short-circuit operator (&&, ||, ??) is now exempt when the left operand is ref-derived (ex: ref.current && setData(1)), matching the existing ref-gated conditional exemption; a left-side setState still runs unconditionally and stays reported. (#​2031)
• react-x/set-state-in-effect: setup identifiers are now collected from the setup argument of the effect call only; the callee and the deps array are no longer scanned, so a function referenced only in the deps array (ex: useEffect(setup, [helper])) is no longer mistaken for the setup and its setState calls stay unattributed. (#​2031)
• react-x/set-state-in-effect: arrow function parameters are no longer collected as callback-body setter references (ex: the setState in useMemo((setState) => ..., [])); only actual callback bodies are collected (ex: useMemo(() => setState, [])). (#​2031)

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.26.4...v5.26.5

v5.26.4

Compare Source

🐞 Fixes

• The name lookup now stops at function boundaries, so expression-bodied factory functions and custom hooks (ex: export const useAnchor = () => useRef(null)) are no longer misreported; calls inside JSX expressions, computed keys, or class static blocks no longer fall back to the outer variable. (#​2029) Closes #​2026.

  Affected rules:

  • react-naming-convention/context-name
  • react-naming-convention/id-name
  • react-naming-convention/ref-name

• The name lookup no longer crosses containers or derived values (ex: const refs = [useRef(null)], const n = useRef(0) + 1), so such calls are no longer reported on the enclosing variable; sequence expressions check only the last value, and unresolvable computed keys (ex: { [key]: useRef(null) }) no longer fall back to the outer variable. (#​2030)

  Affected rules:

  • react-naming-convention/context-name
  • react-naming-convention/id-name
  • react-naming-convention/ref-name

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.26.3...v5.26.4

v5.26.3

Compare Source

🐞 Fixes

• An enclosing object literal property key now takes precedence over the outer assignment target when statically known (ex: const refs = { myRef: useRef(0) }); computed keys with string literals (ex: refs["value"] = useRef(null)) are now checked, and unresolvable computed keys are no longer reported. (#​2028)

  Affected rules:

  • react-naming-convention/context-name
  • react-naming-convention/id-name
  • react-naming-convention/ref-name

• react-naming-convention/ref-name: immediate dereferences of the useRef result through TypeScript type wrappers (ex: (useRef(null) as { current: null }).current, useRef(null)!.current) are no longer reported, extending the #​1375 fix. (#​2028)

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.26.2...v5.26.3

v5.26.2

Compare Source

✨ New

• react-x/no-unused-props: improved prop usage detection. Props parameters with default values (ex: function Component(props: Props = defaultProps)) are now unwrapped and analyzed, props aliased to a local variable (ex: const alias = props) are tracked through the alias, and template literals without substitutions (ex: props[`foo`]) are recognized as static prop keys. (#​2021)

🐞 Fixes

• react-x/no-unused-props: a component whose used prop keys cannot be fully determined (ex: it passes the whole props object to another function) now marks all of its declared props as used, so a props declaration shared with another fully analyzable component is no longer reported as unused. (#​2021)
• react-x/set-state-in-effect: ref-derived values that reach the setState argument through assignment statements (rather than the declaration initializer) are now recognized; only writes that lexically precede the use and live in the use's own function or an ancestor count. (#​2027)
• react-x/set-state-in-effect: parameters of a helper invoked from the effect setup are now treated as ref-derived when the call-site argument is ref-derived, matched per call site by parameter definition. (#​2027)
• react-x/set-state-in-effect: a .current read rooted at a function parameter is now recognized as a ref read (ex: setReferenceElement(anchor?.current) where anchor is a RefObject prop); previously only parameters named ref or ending in Ref were recognized. (#​2027)
• react-x/no-unused-class-component-members: public methods (including function-valued properties) of an exported class component are no longer reported as unused, as they may be part of the component's imperative API invoked by consumers through refs. Data fields, private/protected members, and members of non-exported classes are still reported. (#​2024)

🏗️ Internal

• Ordered message ids by first usage and unified default/suggestion message id naming across react-dom, react-jsx, react-web-api, and react-x rules. (#​2022)

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.26.1...v5.26.2

v5.26.1

Compare Source

🏗️ Internal

• Renamed the internal suggestion message id from "replace" to "suggest".

  Affected rules:

  • react-x/no-context-provider
  • react-x/no-forward-ref
  • react-x/no-use-context

• react-x/immutability: moved context-dependent helpers from helpers.ts into origins.ts and effects.ts to match the fact-based implementation pattern.

• react-x/globals: moved resolveToFunction from helpers.ts to origins.ts.

• Bumped effect to 4.0.3, tsl-dx to 0.14.1, @tsconfig/node20 to 20.1.10, and @types/node to 20.19.43.

📝 Documentation

• Refreshed spec diff verification dates and notes for react-x rules.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.26.0...v5.26.1

v5.26.0

Compare Source

✨ New

• Lowered the minimum required Node.js version from >=22.0.0 to >=20.19.0. (#​2020)

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.25.0...v5.26.0

v5.25.0

Compare Source

✨ New

• react-dom/no-unsafe-target-blank: added an allowReferrer option (default: false). When enabled, rel="noopener" alone is accepted and the suggested fix adds rel="noopener" instead of rel="noreferrer noopener", preserving referrer information while still requiring an explicit token. (#​2019) Closes #​2012.

🏗️ Internal

• @eslint-react/ast: added hasParent and hasEnclosingTryBlock shortcuts to Traverse. (#​2016)
• @eslint-react/ast: renamed the types module to tree and narrowed the Extract.unwrap result type. (#​2017)
• @eslint-react/core: removed the unused REACT_BUILTIN_HOOK_NAMES constant.
• Bumped tsdown to 0.23.1, @effect/platform-node to 4.0.3, pnpm to 12.11.2, @types/node to 26.6.5, setup-uv to v10.3.0, and fumadocs and lucide-react in the website.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.24.10...v5.25.0

v5.24.10

Compare Source

📝 Documentation

• Added a link to the Astryx no-react-introspection rule in the react-x/no-children-count and react-x/no-children-map rule documentation.

🏗️ Internal

• Disabled test isolation in the vitest config.

• Reordered react-web-api/no-leaked-event-listener test specs from typical cases to edge cases. (#​2015)

• Unified KNOWN_-prefixed constant names. (#​2014)

  Affected rules:

  • react-x/no-array-index-key
  • react-x/no-missing-key

• Bumped effect to 4.0.2, @effect/platform-node to 4.0.2, nx to 23.3.0, vite to 8.3.4, lucide-react to 1.53.0, and pnpm to 12.10.1.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.24.9...v5.24.10

v5.24.9

Compare Source

🐞 Fixes

• react-x/set-state-in-effect: optional chaining in a setState argument (ex: setData(ref.current?.value), setWidth(el?.offsetWidth ?? 0) where el is ref-derived) no longer defeats the ref-value exemption; the ChainExpression wrapper is now unwrapped during ref-source detection. (#​2011)

📝 Documentation

• Aligned rule documentation with the current react.dev reference docs. (#​2013)

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.24.8...v5.24.9

v5.24.8

Compare Source

🐞 Fixes

• react-x/rules-of-hooks: removed the incorrect FIX feature declaration; the rule does not provide an auto-fix and is no longer advertised as fixable. (#​2009)

🏗️ Internal

• Added edge-case test specs from the v5.24.7 change review covering react-x/immutability, react-x/set-state-in-render, react-web-api/no-leaked-event-listener, and the leaked-observer rules.
• Bumped next to 16.4.0, vite to 8.3.3, and related dependencies.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.24.7...v5.24.8

v5.24.7

Compare Source

🐞 Fixes

• react-x/immutability: no longer reports rebinding a plain local alias of props/state as a mutation; destructured props rebinding and member writes through aliases are still reported. (#​1995)

• react-x/set-state-in-render: setState calls after nested component or hook declarations are now attributed to the outer component again. (#​2004)

• react-x/set-state-in-render: anonymous callbacks passed directly to memo()/forwardRef() are now treated as component render functions. (#​1998)

• react-web-api/no-leaked-fetch: signal alias chains are now resolved recursively, so fetches with aliased signals correctly pair with their cleanup abort call. (#​1997)

• react-web-api/no-leaked-event-listener: bare global addEventListener(...) calls now pair with matching removeEventListener(...) cleanup calls. (#​1996)

• react-web-api/no-leaked-event-listener: a signal destructured from new AbortController() is now recognized. (#​2001)

• disconnect() / unobserve(...) now only count as cleanup in the cleanup phase; useRef-held observer instances are tracked; unobserve(...) inside the observer callback no longer pairs with observe(...). (#​2002, #​2003)

  Affected rules:

  • react-web-api/no-leaked-resize-observer
  • react-web-api/no-leaked-intersection-observer

🏗️ Internal

• Bumped typescript-eslint to 8.71.1 and postcss to 8.5.29.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.24.6...v5.24.7

v5.24.6

Compare Source

🐞 Fixes

• react-x/no-unused-props: computed member access and destructuring with an identifier key (ex: props[key], const { [key]: value } = props) no longer count as usage of a prop named after the key; the rule now bails out on such dynamic keys instead of reporting actually-used props as unused. (#​1994)
• react-x/set-state-in-effect: object-pattern destructuring of the useState tuple is now resolved by numeric key: a name bound at key 0 (ex: const { 0: value } = useState()) is no longer mistaken for the setter, while key 1 (ex: const { 1: setData } = useState()) is still recognized. (#​1994)
• react-x/set-state-in-render: same useState object-pattern destructuring fix as set-state-in-effect. (#​1994)

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.24.5...v5.24.6

v5.24.5

Compare Source

🏗️ Internal

• Self-linted rule implementations with eslint-plugin-eslint-plugin, removing redundant empty defaultOptions declarations and enforcing meta.defaultOptions for rules with options. (#​1993) Thanks to @​rakleed and @​Rel1cx!

• Minor code cleanups. Thanks to @​Rel1cx!

  Affected rules:

  • react-web-api/no-leaked-intersection-observer
  • react-x/no-create-ref
  • react-x/no-nested-lazy-component-declarations
  • react-x/use-state

• Bumped effect to 4.0.1, pnpm to 12.9.1, fumadocs-core and fumadocs-ui to 16.16.1, lucide-react to 1.52.0, tsl-dx to 0.14.0, and tinybench to 6.2.0. Thanks to @​Rel1cx!

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.24.4...v5.24.5

v5.24.4

Compare Source

🏗️ Internal

• Enable dead-code elimination in tsdown config, producing smaller published packages.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.24.3...v5.24.4

v5.24.3

Compare Source

🏗️ Internal

• @local/eff: minor code optimizations.
• @eslint-react/shared: minor code optimizations.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.24.2...v5.24.3

v5.24.2

Compare Source

🏗️ Internal

• @eslint-react/core, @eslint-react/var, the react-dom plugin, and the react-x plugin: replaced in operator checks with the hasProperty helper from @local/eff.
• @eslint-react/shared: documented getNormalizedSettings.
• JSDoc comments are now stripped from the tsdown build output, producing smaller published packages.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.24.1...v5.24.2

v5.24.1

Compare Source

📝 Documentation

• Added a link to the Astryx no-react-introspection rule in the react-x/no-children-count and react-x/no-children-map rule documentation.

🏗️ Internal

• Disabled test isolation in the vitest config.

• Reordered react-web-api/no-leaked-event-listener test specs from typical cases to edge cases. (#​2015)

• Unified KNOWN_-prefixed constant names. (#​2014)

  Affected rules:

  • react-x/no-array-index-key
  • react-x/no-missing-key

• Bumped effect to 4.0.2, @effect/platform-node to 4.0.2, nx to 23.3.0, vite to 8.3.4, lucide-react to 1.53.0, and pnpm to 12.10.1.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.24.9...v5.24.10

v5.24.0

Compare Source

🐞 Fixes

• react-x/set-state-in-effect: more value shapes are recognized as ref-derived setState arguments: interpolations in template literals (ex: setData(`${ref.current}`)), tagged templates (both the quasi and a ref-derived tag), object and array literals (ex: setData({ value: ref.current })), and spreads (ex: setData({ ...ref.current })) — previously these fell through to the default case and were reported. (#​1988)

📝 Documentation

• Added eslint-config-xo-react to the website's community presets.

🏗️ Internal

• @local/eff: added predicate combinators and type guards synced with effect, and migrated call sites across the workspace to them. (#​1989)

• Reworked to the fact-based implementation pattern — fact collection (collect.ts), provenance resolution (origins.ts), and violation inference (effects.ts) are now separate modules, with lib.ts replaced by a pure-AST helpers.ts; set-state-in-effect again classifies a hook name configured as both additionalStateHooks and additionalEffectHooks as a state hook first. (#​1983, #​1985, #​1986)

  Affected rules:

  • react-x/set-state-in-effect
  • react-x/set-state-in-render
  • react-x/use-memo

• react-x/use-state: aligned the nested-expression collectors' visitor keys to callee-first order, matching eslint-visitor-keys; no behavior change. (#​1988)

• Migrated package unit tests to the shared @local/testkit helpers. (#​1987)

• Renamed message ids to kebab-case across all plugins. (#​1984)

• Bumped fumadocs-core and fumadocs-ui to 16.15.18, fumadocs-mdx to 15.4.6, lucide-react to 1.50.0, and @types/node to 26.6.4.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.23.5...v5.24.0

v5.23.5

Compare Source

🐞 Fixes

• react-x/set-state-in-effect: the ref-derived value exemption now also covers setState calls reached indirectly through functions or hook callbacks invoked from the effect setup, not only setState written directly in the setup body. (#​1982)
• react-x/set-state-in-effect: more ref read shapes are recognized as ref-derived values — <ref-named>.current anywhere in a member chain, locals derived from other ref-derived locals, and reads through a ref/xxxRef parameter. (#​1982)
• react-web-api/no-leaked-event-listener: removeEventListener inside a function called from the effect cleanup now pairs with its addEventListener, fixing false positives for listeners removed on unmount; cleanup calls resolve to the actual functions, so same-named shadowed functions no longer pair by coincidence. (#​1982)

🏗️ Internal

• Bumped effect to 4.0.0 and migrated the repo scripts to the v4 APIs. (#​1981)

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.23.4...v5.23.5

v5.23.4

Compare Source

🐞 Fixes

• Added the missing react-x/static-components rule to the disable-experimental preset. (#​1980)

• Fixed type imports (RuleFeature is now imported from @eslint-react/eslint instead of @eslint-react/shared).

  Affected rules:

  • react-x/exhaustive-deps
  • react-x/rules-of-hooks

📝 Documentation

• react-jsx/no-useless-fragment: clarified the scope of the allowExpressions option and unified experimental-rule callout wording across rule docs.
• react-x: unified cross-rule references in rule docs to full rule names.
• Removed low-relevance entries from the further reading sections of rule docs, and removed a redundant note about eslint being an optional peer dependency.
• Fixed inaccuracies in internal documentation. (#​1980)

🏗️ Internal

• Adopted ts-pattern for type checks in @eslint-react/core, @eslint-react/jsx, and the react-dom plugin, and declared the missing ts-pattern dependencies.
• Added behavior boundary tests for react-jsx/no-useless-fragment.
• Bumped fumadocs-core, fumadocs-ui, and lucide-react in the website.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.23.3...v5.23.4

v5.23.3

Compare Source

🐞 Fixes

• react-x/immutability: reassigning a binding that resolves to component props or state (value = value + "!", count++, including destructuring and for...of rebinding forms) is now reported as a direct mutation, matching upstream react-hooks/immutability; rebinding iterator or shallow-copy bindings remains allowed. (#​1979)
• react-x/set-state-in-effect: ref reads traced through intermediate local computations (ex: const dv = visible - prevVisible.current) are now recognized as ref-derived values, and a preceding early-return guard whose test is ref-derived (ex: if (dv === 0) return;) now exempts the setState calls that follow it — previously only setState nested directly inside a ref-gated if/conditional was exempted. Aligns with react-hooks 7.1.1. (#​1979)

📝 Documentation

• react-x/no-unstable-context-value: documented the React 19 <Context> provider detection heuristic and its name-based limitations. (#​1979)
• Updated the README badges to reference eslint-plugin-react-x.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.23.2...v5.23.3

v5.23.2

Compare Source

🏗️ Internal

• Removed unused dependencies and fixed phantom dependencies across the workspace.
• Bumped next to 16.3.7, fumadocs-core and fumadocs-ui to 16.15.16, and eslint-plugin-package-json to 1.10.1.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.23.1...v5.23.2

v5.23.1

Compare Source

🏗️ Internal

• Re-verified and synchronized the IMPL-SPEC diff reports for the following react-x rules. (#​1977, #​1978)
  • react-x/error-boundaries
  • react-x/globals
  • react-x/immutability
  • react-x/purity
  • react-x/refs
  • react-x/set-state-in-effect
  • react-x/set-state-in-render
  • react-x/use-memo
• Bumped typescript-eslint to 8.71.0, tsl-dx to 0.13.7, and pnpm to 12.8.1.

📝 Documentation

• Added argo-cd, griffel, tanstack/table, and eslint-config-studio to the website's community lists.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.23.0...v5.23.1

v5.23.0

Compare Source

✨ New

• react-x/static-components: dynamic creation-site tracing now follows both sides of logical expressions (ex: const C = DefaultComponent || (() => <div />)) and the last element of sequence expressions (ex: const C = (setup(), () => <div />)), in initializers and reassignments alike. (#​1975)

🐞 Fixes

• react-x/static-components: parameters of nested non-component functions (ex: function render(Comp) { return <Comp /> }) are no longer mistaken for render-created components; definitions are judged by definition type instead of AST node type. (#​1975)
• react-x/static-components: createdHere is now reported once per creation site instead of once per JSX usage; the default diagnostic remains per usage. (#​1975)

🏗️ Internal

• react-x/static-components: restructured the rule to the fact-based implementation pattern — collect.ts (usage facts), origins.ts (creation-site resolution), and effects.ts (effect inference) are now separate modules, with reporting centralized in Program:exit; added 14 boundary test cases covering creation-site resolution, render boundaries, and per-usage reporting. (#​1975)
• Renamed lib.ts to helpers.ts in the fact-based react-x rules (globals, immutability, refs). (#​1976)
• Bumped @effect/language-service to 0.87.3 and oxlint to 1.86.0.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.22.1...v5.23.0

v5.22.1

Compare Source

🐞 Fixes

• react-x/use-state: directly returning the useState result (ex: return React.useState()) is now allowed regardless of the rule's options, matching the exemption in the original react/hook-use-state rule. Covers explicit, implicit (arrow function), and type-asserted returns; lazy initialization checks still apply. (#​1974, closes #​1963)

📝 Documentation

• Added a note about eslint being an optional peer dependency to the READMEs and the website's getting-started guides.
• Simplified the @eslint-react/kit README to point to the full documentation.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.22.0...v5.22.1

v5.22.0

Compare Source

✨ New

• react-dom/no-unknown-property: added React 19.3 properties to the known property allowlist. (#​1973)
  • closedby on dialog
  • onFullscreenChange, onFullscreenError (and their Capture variants), credentialless, and maskType — gated on React version >= 19.3.0
  • onLoad on body
  • onScrollEnd (and its Capture variant)
  • shadowrootmode, shadowrootclonable, shadowrootdelegatesfocus, and shadowrootserializable on template

🏗️ Internal

• Bumped fumadocs-core and fumadocs-ui to 16.15.15.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.21.3...v5.22.0

v5.21.3

Compare Source

🐞 Fixes

• react-x/purity: reverted the v5.21.2 exemption for impure calls in useRef initializer arguments (ex: useRef(document.createElement("div"))); such calls are reported again. (#​1972)

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.21.2...v5.21.3

v5.21.2

Compare Source

🐞 Fixes

• react-x/no-unnecessary-use-prefix: hooks that call other hooks only within nested callbacks, functions named exactly use, and hooks defined in test mock module registrations are no longer reported. (#​1971)
• react-x/no-unused-class-component-members: methods invoked by host environments through refs (React Native's NativeMethods) are no longer reported as unused. (#​1971)
• react-x/purity: async function components in modules without a use client directive and impure calls in useRef initializer arguments are no longer reported. (#​1971)
• react-x/set-state-in-effect: local variables initialized from nested member expressions rooted at a ref are now recognized as ref-derived values and no longer reported. (#​1971)

🏗️ Internal

• @eslint-react/ast: predefined and exported common node-type helpers in the Check namespace and migrated call sites to them.

📝 Documentation

• Website rule docs no longer include the per-rule ## Versions section; a rule's changelog can be viewed directly via the Rule Changelog link under the ## Resources section of each rule doc.

Full Changelog: https://github.com/Rel1cx/eslint-react/compare/v5.21.1...v5.21.2

v5.21.1

Compare Source

🐞 Fixes

• Fixed missed reports where a timer, fetch controller, or observer created in one effect was treated as cleaned up because an unrelated cleanup in another effect referenced a different variable with the same name; identifier matching now resolves both sides to their variables by scope instead of comparing names only. (#​1969)

  Affected rules:

  • react-web-api/no-leaked-timeout
  • react-web-api/no-leaked-interval
  • react-web-api/no-leaked-fetch
  • react-web-api/no-leaked-resize-observer
  • react-web-api/no-leaked-intersection-observer

🏗️ Internal

• Simplified the react-web-api leaked-resource rules by replacing manual function-context stack tracking with Traverse.findParent ancestor lookup, and added boundary tests covering deeply nested callbacks, cross-effect pairing, and wrapped or referenced setup callbacks. (#​1969)

  Affected rules:

  • react-web-api/no-leaked-timeout

[!IMPORTANT] ✂ PR body was truncated to here.