`react-doctor/no-conflicting-spring-options`

Motion spring mixes incompatible option modes

Category: Bugs
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/no-conflicting-spring-options. 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";

const Card = () => (
  <motion.div
    transition={{
      type: "spring",
      stiffness: 300,
      damping: 24,
      duration: 0.4,
    }}
  />
);

Corrected pattern

import { motion } from "motion/react";

const Card = () => (
  <motion.div
    transition={{
      type: "spring",
      stiffness: 300,
      damping: 24,
    }}
  />
);

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/no-conflicting-spring-options diagnostic in the current repository. Required change: - Choose either stiffness/damping/mass or duration/bounce for a Motion spring so every configured value takes effect.

Reference transformation:Before:

import { motion } from "motion/react";

const Card = () => (
  <motion.div
    transition={{
      type: "spring",
      stiffness: 300,
      damping: 24,
      duration: 0.4,
    }}
  />
);

After:

import { motion } from "motion/react";

const Card = () => (
  <motion.div
    transition={{
      type: "spring",
      stiffness: 300,
      damping: 24,
    }}
  />
);

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. 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/no-controlled-input-value-without-state-update: Controlled input value is a fixed literal
react-doctor/no-create-context-in-render: Move createContext to module scope so its Context identity stays stable across renders
react-doctor/no-create-object-url-in-render: Object URL is created during render
react-doctor/no-create-ref-in-function-component: createRef in function component
react-doctor/no-create-store-in-render: Hoist the store/atom/observable construction to module scope: const store = create(...) outside the component.

react-doctor/no-conflicting-spring-options