`react-doctor/motion-animate-presence-must-outlive-child`

AnimatePresence unmounts with its exiting child

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-animate-presence-must-outlive-child. 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 { AnimatePresence, motion } from "motion/react";

{isOpen && (
  <AnimatePresence>
    <motion.dialog exit={{ opacity: 0 }} />
  </AnimatePresence>
)}

Corrected pattern

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

<AnimatePresence>
  {isOpen && <motion.dialog key="dialog" exit={{ opacity: 0 }} />}
</AnimatePresence>

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-animate-presence-must-outlive-child diagnostic in the current repository. Required change: - Keep AnimatePresence mounted and place the condition around its child so Motion can observe and animate the child leaving.

Reference transformation:Before:

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

{isOpen && (
  <AnimatePresence>
    <motion.dialog exit={{ opacity: 0 }} />
  </AnimatePresence>
)}

After:

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

<AnimatePresence>
  {isOpen && <motion.dialog key="dialog" exit={{ opacity: 0 }} />}
</AnimatePresence>

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-animate-presence-requires-key: AnimatePresence child is missing a key
react-doctor/motion-animate-presence-wait-single-child: AnimatePresence wait mode has multiple children
react-doctor/motion-create-in-render: Motion component is created during render
react-doctor/motion-drag-axis-constraint-mismatch: Motion drag constraints do not match the drag axis
react-doctor/motion-imperative-animation-in-render: Imperative Motion animation runs during render

react-doctor/motion-animate-presence-must-outlive-child