react-doctor/motion-animate-presence-requires-key

Give each direct AnimatePresence child a stable identity when multiple direct elements can coexist

Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

For react-doctor/motion-animate-presence-requires-key, the detector first proves AnimatePresence is imported from framer-motion or motion/react. It counts only direct JSXElement children and ignores whitespace and expression containers. It reports when two or more direct elements include one without a static key. Conditional expressions, logical expressions, fragments, and map calls are not counted as direct elements, so absence of a report does not validate those shapes. Confirm that the reported elements can coexist and that each key represents stable, unique semantic identity across renders. The Before example is representative, not exhaustive.

Evidence boundary

The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

Record one outcome:

• Confirmed failure: The required evidence establishes the violation.
• Rejected: A documented exception or false-positive predicate applies.
• Needs evidence: Named evidence can still be collected.
• Unavailable: Required evidence cannot be collected in this run.
• Waived with evidence: An authorized, scoped exception applies to an established failure.
• Observation: The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.

Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.

Review a candidate correction

Apply this candidate correction only after the required evidence confirms the risk.

Reported pattern

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

const Demo = () => (
  <AnimatePresence>
    <motion.main />
    <motion.dialog key="dialog" exit={{ opacity: 0 }} />
  </AnimatePresence>
);

Candidate corrected pattern

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

const Demo = () => (
  <AnimatePresence>
    <motion.main key="page" />
    <motion.dialog key="dialog" exit={{ opacity: 0 }} />
  </AnimatePresence>
);

Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

Add a stable identity key only to the reported direct child. Reuse an existing record ID, route, mode, or domain identity. Do not use an array index, random value, or value that changes per render. Preserve the child's element type, exit animation, ordering, and AnimatePresence mode. If the children are not distinct states, simplify the structure instead of inventing keys. See https://motion.dev/docs/react-animate-presence

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.

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

const Demo = () => (
  <AnimatePresence>
    <motion.main />
    <motion.dialog key="dialog" exit={{ opacity: 0 }} />
  </AnimatePresence>
);

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

const Demo = () => (
  <AnimatePresence>
    <motion.main key="page" />
    <motion.dialog key="dialog" exit={{ opacity: 0 }} />
  </AnimatePresence>
);