# `react-doctor/exhaustive-deps`

Match the deps array to what the hook callback actually captures, or stabilize/move recreated values instead of blindly adding them.

- **Status:** Active
- **Category:** Correctness
- **Assessment:** Evidence-required risk
- **Required evidence:** source code
- **Default configuration:** Enabled
- **Default severity:** warn
- **Scope:** All supported frameworks
- **Active when:** always
- **Requirements:** react
- **Tags:** test-noise
- **Priority:** 66 (P2)
- **Source:** oxlint-plugin-react-doctor
- **Rule set:** oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
- **Documentation:** [Official documentation](https://oxc.rs/docs/guide/usage/linter/rules/react/exhaustive-deps)

## Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

Fires on `useEffect`, `useLayoutEffect`, `useInsertionEffect`, `useCallback`, `useMemo`, `useImperativeHandle`, and configured additional hooks when the dependency array omits a reactive capture or contains an invalid dependency. Effects may intentionally omit the array, and unused reactive effect dependencies are allowed. `useMemo` and `useCallback` require dependency arrays and report unused dependencies. All supported hooks report duplicates, spreads, literals, computed members, `ref.current`, `useEffectEvent`, inline-recreated values, and outer-variable assignments. Stable setters, dispatch, `startTransition`, ref bindings, effect-event handlers, module imports, and primitive local constants do not need dependencies.

## Evidence boundary

The diagnostic proves only that the detector's modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, explicit repository policy, relevant exceptions, and required rendered or runtime evidence before deciding the occurrence. This page’s Assessment and Required evidence fields define the review contract.

Default severity is registry metadata. Use the occurrence's JSON severity after repository configuration when ordering real findings.

Record one outcome:

- **Confirmed failure:** The required evidence establishes the violation.
- **Rejected:** A documented exception or false-positive predicate applies.
- **Needs evidence:** Named evidence can still be collected.
- **Unavailable:** Required evidence cannot be collected in this run.
- **Waived with evidence:** An authorized, scoped exception applies to an established failure.
- **Observation:** The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review or expiry condition. It is not a pass or false positive.

## Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

Add every reactive capture when you provide a dependency array. Keep the required arrays on `useMemo` and `useCallback`; an effect may intentionally run after every render without one. Move recreated values into the callback or stabilize them before adding them. Use functional state updates to remove captured state, depend on the ref instead of `ref.current`, and avoid spreads or computed expressions. Add a narrow suppression with a written reason only when exclusion is intentional. See https://oxc.rs/docs/guide/usage/linter/rules/react/exhaustive-deps

## Repository-wide copy prompt

Use this only for a repository-wide pass after validating each occurrence. For one occurrence, use the occurrence-level guidance above.

````text
Fix every confirmed `react-doctor/exhaustive-deps` diagnostic in the current repository.

Required change:
- Add every reactive capture when you provide a dependency array. Keep the required arrays on `useMemo` and `useCallback`; an effect may intentionally run after every render without one. Move recreated values into the callback or stabilize them before adding them. Use functional state updates to remove captured state, depend on the ref instead of `ref.current`, and avoid spreads or computed expressions. Add a narrow suppression with a written reason only when exclusion is intentional. See https://oxc.rs/docs/guide/usage/linter/rules/react/exhaustive-deps.

Validation before editing:
Fires on `useEffect`, `useLayoutEffect`, `useInsertionEffect`, `useCallback`, `useMemo`, `useImperativeHandle`, and configured additional hooks when the dependency array omits a reactive capture or contains an invalid dependency. Effects may intentionally omit the array, and unused reactive effect dependencies are allowed. `useMemo` and `useCallback` require dependency arrays and report unused dependencies. All supported hooks report duplicates, spreads, literals, computed members, `ref.current`, `useEffectEvent`, inline-recreated values, and outer-variable assignments. Stable setters, dispatch, `startTransition`, ref bindings, effect-event handlers, module imports, and primitive local constants do not need dependencies.

Constraints:
- Make the smallest change that fixes the root cause.
- Preserve behavior and interfaces unrelated to this diagnostic.
- Reuse existing project components, utilities, and conventions.
- Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations.
- Adapt identifiers and framework details instead of copying blindly.
- Do not disable the rule or suppress matching code.

Assessment:
- Record detector evidence, applicability facts, assumptions, missing evidence, and the rule class for this occurrence.
- Return one outcome: Confirmed failure, Rejected, Needs evidence, Unavailable, Waived with evidence, or Observation.
- A waiver records the established failure, scope, authority, evidence, and review or expiry condition. It is not a pass or false positive.

Verification:
- Run focused tests for the changed behavior.
- Run React Doctor and confirm this diagnostic no longer appears from changed code.
- Run an unfiltered scan of the affected scope before claiming no cross-category regression.
- Report the files changed and any checks you could not run.
````