`react-doctor/react-router-no-navigate-in-render`

navigate() called during render

Category: Bugs
Severity: error
Source: oxlint-plugin-react-doctor
Framework: global
Enabled when: react-router
Tags: test-noise
Default: Enabled

Validate the diagnostic

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

Confirm the reported code matches react-doctor/react-router-no-navigate-in-render. 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 Account = ({ user }) => {
  const navigate = useNavigate();
  if (!user) navigate("/login");
  return <Profile user={user} />;
};

Corrected pattern

const Account = ({ user }) => {
  if (!user) return <Navigate to="/login" replace />;
  return <Profile user={user} />;
};

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/react-router-no-navigate-in-render diagnostic in the current repository. Required change: - Render <Navigate> for declarative redirects, redirect from a loader or action, or navigate from an event or effect.

Reference transformation:Before:

const Account = ({ user }) => {
  const navigate = useNavigate();
  if (!user) navigate("/login");
  return <Profile user={user} />;
};

After:

const Account = ({ user }) => {
  if (!user) return <Navigate to="/login" replace />;
  return <Profile user={user} />;
};

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. - 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: react-router. 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 Bugs rules from the rules reference:

react-doctor/react-router-no-nested-router: Router nested inside another router
react-doctor/react-router-no-redirect-in-try-catch: redirect() inside try-catch
react-doctor/react-router-no-route-module-environment-suffix: Route module has an environment suffix
react-doctor/react-router-no-router-in-render: Router created during render
react-doctor/react-router-no-session-mutation-in-loader: Loader mutates session state

react-doctor/react-router-no-navigate-in-render