`react-doctor/r3f-no-advancing-clock-in-use-frame`

Clock advanced inside useFrame

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

Validate the diagnostic

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

Confirm the reported code matches react-doctor/r3f-no-advancing-clock-in-use-frame. 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

useFrame(({ clock }) => {
  mesh.current.rotation.y += clock.getDelta();
});

Corrected pattern

useFrame((_, delta) => {
  mesh.current.rotation.y += delta;
});

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/r3f-no-advancing-clock-in-use-frame diagnostic in the current repository. Required change: - Use the delta argument supplied to useFrame or read clock.elapsedTime without advancing the shared clock.

Reference transformation:Before:

useFrame(({ clock }) => {
  mesh.current.rotation.y += clock.getDelta();
});

After:

useFrame((_, delta) => {
  mesh.current.rotation.y += delta;
});

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. - Do not edit code when this condition applies: r3f:10. 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/r3f-no-async-use-frame: Async useFrame callback
react-doctor/r3f-no-dispose-loader-cache: Disposal of a cached R3F loader asset
react-doctor/r3f-no-duplicate-primitive-object: Primitive object mounted twice
react-doctor/r3f-no-extend-in-render: R3F catalogue extension during render
react-doctor/r3f-no-fresh-portal-container: Fresh R3F portal container

react-doctor/r3f-no-advancing-clock-in-use-frame