react-doctor/react-in-jsx-scope

If on React 17+ with the new JSX transform, disable this rule; otherwise import React at the top of the file.

Validation prompt

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

Fires once per JSX usage (any JSXOpeningElement or JSXFragment) in a file where the identifier React is not bound anywhere in the module: relevant only to the classic JSX transform, which expands <a/> to React.createElement('a'). The check has no scope analysis: any module-level binding named React (import, var, function param, etc.) suppresses it for the whole file, matching OXC.

Suppress when: projects on React 17+ using the automatic runtime (tsconfig jsx: "react-jsx" or Babel runtime: "automatic") never need React in scope, so every finding here is a non-issue and the rule should simply be off.

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, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

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 condition. It is not a pass or false positive.

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

Fix prompt

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

If the project targets the automatic JSX runtime (React 17+ with tsconfig jsx: "react-jsx" or Babel runtime: "automatic"), disable this rule rather than adding imports: React is injected for you. If you are genuinely on the classic transform, add import React from 'react'; at the top of the file so React.createElement resolves. See https://oxc.rs/docs/guide/usage/linter/rules/react/react-in-jsx-scope

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.