# `react-doctor/r3f-no-internal-imports`

Private R3F import

- **Category:** Maintainability
- **Severity:** warn
- **Source:** oxlint-plugin-react-doctor
- **Framework:** global
- **Enabled when:** react, r3f

## Validate the diagnostic

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

Confirm the reported code matches `react-doctor/r3f-no-internal-imports`. 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

```ts
import {
  createRoot,
} from "@react-three/fiber/dist/declarations/src/core";
```

### Corrected pattern

```ts
import { createRoot } from "@react-three/fiber";
```

## 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/r3f-no-internal-imports` diagnostic in the current repository.

Required change:
- Import from @react-three/fiber or one of its documented public entry points instead of a dist or src implementation path.

Reference transformation:

Before:
```ts
import {
  createRoot,
} from "@react-three/fiber/dist/declarations/src/core";
```

After:
```ts
import { createRoot } from "@react-three/fiber";
```

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

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