`react-doctor/prefer-motion-transform-property`

Motion individual transforms miss compositor acceleration

Category: Performance
Severity: warn
Source: oxlint-plugin-react-doctor
Framework: global
Enabled when: react
Tags: design, opt-in
Default: Disabled until configured

Validate the diagnostic

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

Confirm the reported code matches react-doctor/prefer-motion-transform-property. 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

import { motion } from "motion/react";

<motion.div
  animate={{ x: 120, scale: 1.1 }}
/>

Corrected pattern

import { motion } from "motion/react";

<motion.div
  animate={{
    transform: "translateX(120px) scale(1.1)",
  }}
/>

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/prefer-motion-transform-property diagnostic in the current repository. Required change: - For animation that must remain smooth while JavaScript is busy, animate one transform string instead of Motion's individual transform keys.

Reference transformation:Before:

import { motion } from "motion/react";

<motion.div
  animate={{ x: 120, scale: 1.1 }}
/>

After:

import { motion } from "motion/react";

<motion.div
  animate={{
    transform: "translateX(120px) scale(1.1)",
  }}
/>

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. - Use existing brand assets, product facts, content, and design tokens. - Do not invent claims, customer data, typefaces, or artwork. - 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. 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 Performance rules from the rules reference:

react-doctor/prefer-stable-empty-fallback: Hoist a module-level const EMPTY = [] (or {}) and use it as the || / ?? fallback so the memoised child sees a stable reference
react-doctor/r3f-cap-device-pixel-ratio: Unbounded device pixel ratio
react-doctor/r3f-limit-shadowed-point-lights: Too many shadow-casting point lights
react-doctor/r3f-no-allocation-in-pointer-move: Allocation inside an R3F pointer-move handler
react-doctor/r3f-no-clone-in-use-frame: Three.js clone inside useFrame

react-doctor/prefer-motion-transform-property