`react-doctor/motion-value-constructor-in-render`

Motion value is recreated during render

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

Validate the diagnostic

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

Confirm the reported code matches react-doctor/motion-value-constructor-in-render. 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, motionValue } from "motion/react";

const Slider = () => {
  const x = motionValue(0);
  return <motion.div style={{ x }} />;
};

Corrected pattern

import { motion, useMotionValue } from "motion/react";

const Slider = () => {
  const x = useMotionValue(0);
  return <motion.div style={{ x }} />;
};

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/motion-value-constructor-in-render diagnostic in the current repository. Required change: - Use useMotionValue inside React components, or create a manual motionValue outside the render path.

Reference transformation:Before:

import { motion, motionValue } from "motion/react";

const Slider = () => {
  const x = motionValue(0);
  return <motion.div style={{ x }} />;
};

After:

import { motion, useMotionValue } from "motion/react";

const Slider = () => {
  const x = useMotionValue(0);
  return <motion.div style={{ x }} />;
};

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: 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/no-array-index-key: Use a stable, data-derived key instead of the array iteration index.
react-doctor/no-barrel-import: Import from the direct path: `import { Button } from './components/Button'` instead of `./components`
react-doctor/no-create-object-url-without-revoke: createObjectURL without revokeObjectURL
react-doctor/no-document-write: document.write/writeln
react-doctor/no-dynamic-import-path: Use a string-literal path: `import('./feature/heavy.js')` so the bundler can split this chunk

react-doctor/motion-value-constructor-in-render