react-doctor/only-export-components

Move non-component exports out of files that export components.

Validation prompt

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

Fires only in .tsx/.jsx files (or .js with checkJS) that also export at least one React component, when the same module also exports a non-component value (utility fn, object, enum, createContext result), uses export *, ships an anonymous/unnamed default export, or defines a local component alongside exports: anything that breaks Vite/react-refresh Fast Refresh boundaries. Stable constants are NOT flagged (allowConstantExport defaults true), and use[A-Z] hook exports plus names in allowExportNames are always allowed.

Suppress when: files conventionally exempted by basename (main/index/bootstrap entrypoints, icons/assets/utils/constants/types/hooks/*ShapeUtil/*Node files, test/spec/stories/cypress) are skipped, so a finding on such a path is likely stale or a misclassified filename.

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.

Split the module so the component file exports only components (and constants/hooks if your toolchain allows them): move utility functions, enums, objects, and createContext(...) calls into a sibling non-component file and re-import them (import { ChatContext } from './context'). Name anonymous defaults (export default function Foo() {} instead of export default () => {}), and replace export * with explicit named exports. If a non-component export is genuinely HMR-safe (e.g. a Remix loader/meta), add it to the rule's allowExportNames setting rather than disabling the rule. See https://oxc.rs/docs/guide/usage/linter/rules/react/only-export-components

Repository-wide copy prompt

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