# `react-doctor/three-no-allocation-in-pointer-move`

Three.js allocation inside pointer-move handler

- **Category:** Performance
- **Severity:** warn
- **Source:** oxlint-plugin-react-doctor
- **Framework:** global
- **Enabled when:** three

## Validate the diagnostic

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

Confirm the reported code matches `react-doctor/three-no-allocation-in-pointer-move`. 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
const onPointerMove = (event) => {
  raycaster.setFromCamera(new Vector2(event.x, event.y), camera);
};
```

### Corrected pattern

```ts
const pointer = new Vector2();
const onPointerMove = (event) => {
  pointer.set(event.x, event.y);
  raycaster.setFromCamera(pointer, camera);
};
```

## 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/three-no-allocation-in-pointer-move` diagnostic in the current repository.

Required change:
- Reuse vectors, raycasters, and other Three.js objects while handling continuous pointer movement.

Reference transformation:

Before:
```ts
const onPointerMove = (event) => {
  raycaster.setFromCamera(new Vector2(event.x, event.y), camera);
};
```

After:
```ts
const pointer = new Vector2();
const onPointerMove = (event) => {
  pointer.set(event.x, event.y);
  raycaster.setFromCamera(pointer, camera);
};
```

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

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