react-doctor/jsx-filename-extension

Use .jsx / .tsx (or your project's chosen extension) for files containing JSX.

Validation prompt

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

Fires when a JSXElement or JSXFragment appears in a file whose extension is not in the allowed set (default .jsx, .tsx), reporting once per file on the first JSX node. In allow: "as-needed" mode it additionally fires on an allowed-extension file that contains zero JSX: unless ignoreFilesWithoutCode is set and the file has no non-comment statements.

Suppress when: this is a pure filename-convention check, so JSX in a .js file is flagged even though setups like Next.js and Create React App compile JSX in .js out of the box: suppress when the project intentionally allows JSX in that extension. (Note: Vite/esbuild is NOT such a setup: it errors on JSX in .js by default and effectively agrees with this rule.)

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.

Rename the file to an allowed JSX extension so its contents match its name: e.g. Button.js -> Button.tsx (or .jsx for plain JS), updating any imports that reference the old path. If your toolchain intentionally permits JSX in .js/.ts, instead add that extension under this port's setting settings["react-doctor"].jsxFilenameExtension.extensions (e.g. extensions: ["js", "jsx", "tsx"]) rather than renaming. See https://oxc.rs/docs/guide/usage/linter/rules/react/jsx-filename-extension

Repository-wide copy prompt

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