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

react-doctor/no-pulsing-status-dot

Decorative status dot pulses continuously

  • Category: Maintainability
  • Severity: warn
  • Source: oxlint-plugin-react-doctor
  • Framework: global
  • Enabled when: tailwind
  • Tags: design, test-noise, react-jsx-only
  • 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-pulsing-status-dot. 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

<header>
  <span className="size-2 rounded-full bg-green-500 animate-pulse" />
</header>

Corrected pattern

<span className="inline-flex items-center gap-2">
  <span className="size-2 rounded-full bg-green-500" />
  Online
</span>;

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-pulsing-status-dot diagnostic in the current repository. Required change: - Use a static status indicator unless the element communicates real work in progress.
Reference transformation:Before:
<header>
  <span className="size-2 rounded-full bg-green-500 animate-pulse" />
</header>
After:
<span className="inline-flex items-center gap-2">
  <span className="size-2 rounded-full bg-green-500" />
  Online
</span>;
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. - Confirm this rule is enabled for the project: tailwind. 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:

  • react-doctor/no-pure-black-background: Tint the background slightly toward your brand hue — e.g. `#0a0a0f` or Tailwind's `bg-gray-950`. Pure black looks harsh on modern displays
  • react-doctor/no-pure-black-shadow: Surface uses a pure-black shadow
  • react-doctor/no-radial-halo: Saturated radial halo on a dark surface
  • react-doctor/no-react-children: Pass children as props or render them directly instead of calling React.Children methods.
  • react-doctor/no-react-dom-deprecated-apis: Switch the legacy `react-dom` root API (`render` / `hydrate` / `unmountComponentAtNode`) to `createRoot` / `hydrateRoot` / `root.unmount()` from `react-dom/client`. Replace `findDOMNode` with a ref. The whole `react-dom/test-utils` entry point is removed in React 19 — use `act` from `react` and `fireEvent` / `render` from `@testing-library/react`. Only enabled on projects detected as React 18+.