`react-doctor/three-no-async-animation-loop`

Async Three.js animation callback

Category: Bugs
Severity: warn
Source: oxlint-plugin-react-doctor
Framework: global
Enabled when: three
Tags: three, webgl
Default: Enabled

Validate the diagnostic

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

Confirm the reported code matches react-doctor/three-no-async-animation-loop. 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

renderer.setAnimationLoop(async () => {
  scene.add(await loadNextObject());
  renderer.render(scene, camera);
});

Corrected pattern

const nextObject = await loadNextObject();
scene.add(nextObject);
renderer.setAnimationLoop(() => {
  renderer.render(scene, 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.

Fix every confirmed react-doctor/three-no-async-animation-loop diagnostic in the current repository. Required change: - Keep animation callbacks synchronous; start asynchronous work outside the loop and consume completed state during frames.

Reference transformation:Before:

renderer.setAnimationLoop(async () => {
  scene.add(await loadNextObject());
  renderer.render(scene, camera);
});

After:

const nextObject = await loadNextObject();
scene.add(nextObject);
renderer.setAnimationLoop(() => {
  renderer.render(scene, 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. - 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.

More Bugs rules from the rules reference:

react-doctor/three-on-before-compile-require-program-cache-key: onBeforeCompile variant lacks a program cache key
react-doctor/three-raw-shader-require-fragment-float-precision: Raw fragment shader lacks float precision
react-doctor/three-raw-shader-require-glsl3-version: Raw shader uses GLSL 3 syntax without GLSL3
react-doctor/three-require-animation-mixer-cleanup: Unreleased Three.js animation mixer actions
react-doctor/three-require-controls-cleanup: Undisposed imperative Three.js controls

react-doctor/three-no-async-animation-loop