# `react-doctor/react-router-prefer-route-lazy`

React.lazy creates a route-module waterfall

- **Category:** Performance
- **Severity:** warn
- **Source:** oxlint-plugin-react-doctor
- **Framework:** global
- **Enabled when:** react, react-router:6.9
- **Disabled when:** react-router-framework

## Validate the diagnostic

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

Confirm the reported code matches `react-doctor/react-router-prefer-route-lazy`. 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

```tsx
import { Component } from "./settings";
const route = { path: "/settings", Component };
```

### Corrected pattern

```tsx
const route = {
  path: "/settings",
  lazy: () => import("./settings"),
};
```

## 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.

````text
Fix every confirmed `react-doctor/react-router-prefer-route-lazy` diagnostic in the current repository.

Required change:
- Load route modules with the route lazy property so initial navigation does not download every route component.

Reference transformation:

Before:
```tsx
import { Component } from "./settings";
const route = { path: "/settings", Component };
```

After:
```tsx
const route = {
  path: "/settings",
  lazy: () => import("./settings"),
};
```

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.
- Preserve resource ownership and cleanup. Do not move work into a hotter render or frame path.
- 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, react-router:6.9`.
- Do not edit code when this condition applies: react-router-framework.

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.
````