New
Introducing React Bench, see how different models perform on React code

react-doctor/no-common-root-font

Page root uses a generic default font choice

  • Category: Maintainability
  • Severity: warn
  • Source: oxlint-plugin-react-doctor
  • Framework: global
  • Enabled when: always
  • Tags: design, test-noise
  • Default: Disabled until configured

Validate the diagnostic

Confirm the reported code matches this rule before you edit it.

Confirm the reported code matches react-doctor/no-common-root-font. Compare it with the Before example and verify the same API, framework, and execution context. Treat it as a false positive only when one of those conditions differs.

Compare the code

The corrected pattern shows a focused way to address the diagnostic.

Reported pattern

const Page = () => (
  <main style={{ fontFamily: "Inter, sans-serif" }}>
    Project diagnostics
  </main>
);

Corrected pattern

const Page = () => <main>Project diagnostics</main>;

How to fix

Use the corrected pattern as a reference. Preserve behavior that the rule does not require you to change.

Copyable fix prompt

Copy this self-contained prompt into your coding agent after you confirm the diagnostic.

Fix every confirmed react-doctor/no-common-root-font diagnostic in the current repository. Required change: - Use the project’s existing brand typography token. If none exists, remove the arbitrary root override and inherit the established typography instead of inventing a typeface.
Reference transformation:Before:
const Page = () => (
  <main style={{ fontFamily: "Inter, sans-serif" }}>
    Project diagnostics
  </main>
);
After:
const Page = () => <main>Project diagnostics</main>;
Constraints: - Confirm the reported code matches the Before pattern. - 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. - Use existing brand assets, product facts, content, and design tokens. - Do not invent claims, customer data, typefaces, or artwork. - Adapt identifiers and framework details instead of copying blindly. - Do not disable the rule or suppress matching code. Verification: - Run focused tests for the changed behavior. - Run React Doctor and confirm this diagnostic no longer appears. - Report the files changed and any checks you could not run.

More Maintainability rules from the rules reference: