react-doctor/rn-prefer-expo-image
In an Expo-managed file, consider expo-image for non-static Image or ImageBackground usage while preserving layout and overlay semantics
- Status
- Active
- Category
- React Native
- Assessment
- Evidence-required risk
- Required evidence
- source code
- Default configuration
- Enabled
- Default severity
- warn
Show technical metadata
- Scope
- React Native
- Active when
- Expo-managed file with non-static react-native Image or ImageBackground usage
- Requirements
- expo
- Tags
- react-native, test-noise
- Priority
- 34 (P3)
- Source
- oxlint-plugin-react-doctor
- Rule set
- oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
Validation prompt
Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.
Confirm the detector is running on an Expo-managed file and the named value import is Image or ImageBackground from "react-native". It reports an import only when at least one observed use is not proven to use a bundled static asset; imports used exclusively with statically resolved bundled images are excluded. Confirm expo-image is already installed or dependency and native-configuration changes are authorized. ImageBackground is not a drop-in Image migration because its children and container layout must be preserved.
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 React Native Image, migrate deliberately to Image from "expo-image" only when the dependency is present or its installation is authorized; preserve source selection, sizing, accessibility, resize behavior, callbacks, and recycled-list behavior, mapping resizeMode to contentFit only when semantics match. For ImageBackground, preserve children with an outer View and a positioned Expo Image, including the original container dimensions, image styling, clipping, accessibility, and overlay order; otherwise keep ImageBackground. Do not replace ImageBackground with a childless Image or add Expo/native configuration without authorization. See https://docs.expo.dev/versions/latest/sdk/image/
Repository-wide copy prompt
Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.
Show repository-wide prompt
Fix every confirmed react-doctor/rn-prefer-expo-image diagnostic in the current repository.
Required change:
- For React Native Image, migrate deliberately to Image from "expo-image" only when the dependency is present or its installation is authorized; preserve source selection, sizing, accessibility, resize behavior, callbacks, and recycled-list behavior, mapping resizeMode to contentFit only when semantics match. For ImageBackground, preserve children with an outer View and a positioned Expo Image, including the original container dimensions, image styling, clipping, accessibility, and overlay order; otherwise keep ImageBackground. Do not replace ImageBackground with a childless Image or add Expo/native configuration without authorization. See https://docs.expo.dev/versions/latest/sdk/image/.
Validation before editing:
Confirm the detector is running on an Expo-managed file and the named value import is Image or ImageBackground from "react-native". It reports an import only when at least one observed use is not proven to use a bundled static asset; imports used exclusively with statically resolved bundled images are excluded. Confirm expo-image is already installed or dependency and native-configuration changes are authorized. ImageBackground is not a drop-in Image migration because its children and container layout must be preserved.
Constraints:
- 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.
- Before editing, inspect the manifest, lockfile, native app configuration, React Native and Expo versions, and New Architecture status.
- Also inspect the Reanimated major, installed list-library majors, and every affected platform-specific file.
- Do not add or upgrade a native dependency, change linking, or alter Pods/Gradle setup unless explicitly authorized.
- Do not enable the New Architecture or change Expo/native configuration unless explicitly authorized.
- Preserve navigation, gesture, keyboard, safe-area, accessibility, lifecycle, and platform semantics; do not treat them as file-local import substitutions.
- Verify behavior in a release build on each affected device platform in scope. Name any unavailable platform instead of claiming it passed.
- 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:
Expo-managed file with non-static react-native Image or ImageBackground usage.
Assessment:
- Record detector evidence, applicability facts, assumptions, missing evidence, and the rule class for this occurrence.
- Return one outcome: Confirmed failure, Rejected, Needs evidence, Unavailable, Waived with evidence, or Observation.
- A waiver records the established failure, scope, authority, evidence, and review or expiry condition. It is not a pass or false positive.
Verification:
- Run focused tests for the changed behavior.
- Run React Doctor and confirm this diagnostic no longer appears from changed code.
- Run an unfiltered scan of the affected scope before claiming no cross-category regression.
- Report the files changed and any checks you could not run.