`react-doctor/motion-unstable-layout-id-in-iteration`

Motion layout ID is unstable in an iteration

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

Validate the diagnostic

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

Confirm the reported code matches react-doctor/motion-unstable-layout-id-in-iteration. 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";

{items.map((item) => (
  <motion.article key={item.id} layoutId="card" />
))}

Corrected pattern

import { motion } from "motion/react";

{items.map((item) => (
  <motion.article key={item.id} layoutId={`card-${item.id}`} />
))}

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-unstable-layout-id-in-iteration diagnostic in the current repository. Required change: - Derive repeated layout IDs from stable item identity, or scope each repeated component with a LayoutGroup ID derived from the item.

Reference transformation:Before:

import { motion } from "motion/react";

{items.map((item) => (
  <motion.article key={item.id} layoutId="card" />
))}

After:

import { motion } from "motion/react";

{items.map((item) => (
  <motion.article key={item.id} layoutId={`card-${item.id}`} />
))}

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. 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/motion-use-transform-range-length: Motion transform ranges have different lengths
react-doctor/motion-value-subscription-in-render: Motion value subscription is created during render
react-doctor/nextjs-async-client-component: Fetch data in a parent Server Component and pass it as props, or use useQuery/useSWR in the client component
react-doctor/nextjs-async-dynamic-api-not-awaited: Synchronous Next.js request API access
react-doctor/nextjs-error-boundary-missing-use-client: Add `'use client'` as the first statement of error.tsx / global-error.tsx so the error boundary becomes a Client Component.

react-doctor/motion-unstable-layout-id-in-iteration