react-doctor/use-lazy-motion

Consider LazyMotion for routes that ship the full Motion component; verify the installed package, required features, and measured bundle impact

Validation prompt

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

The detector reports a non-type named motion import from exactly "framer-motion" or "motion/react"; it does not measure the produced chunk, feature usage, route boundary, or an existing LazyMotion provider elsewhere. Current Motion documentation quotes Rollup-generated reference sizes, which are not universal across versions and bundlers. Confirm the import reaches the affected client bundle and inventory drag, pan, layout projection, gestures, and mixed motion/m descendants. Suppress when the route is already isolated behind an appropriate dynamic boundary, the installed version has a different supported API, domMax leaves no material saving, or a bundle report shows no worthwhile reduction.

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.

Fix prompt

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

For the current motion package, import { LazyMotion, domAnimation } from "motion/react", import * as m from "motion/react-m", wrap the relevant client subtree once in <LazyMotion features={domAnimation}>, and replace Motion components in that subtree with m.*. Use domMax when the subtree needs pan, drag, or layout animation. Add LazyMotion strict mode only after every descendant is converted, because importing/rendering the full motion component defeats the split. For an existing framer-motion dependency, use the API supported by its installed version instead of silently migrating packages. Preserve client/server and code-splitting boundaries, then compare the actual route chunk before and after. See https://motion.dev/docs/react-reduce-bundle-size

Repository-wide copy prompt

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