react-doctor/no-srcset-without-sizes
Responsive image omits sizes
- Category: Performance
- Severity: warn
- Source:
oxlint-plugin-react-doctor - Framework: global
- Enabled when: react
- Default: Enabled
Validate the diagnostic
Confirm the reported code matches this rule before you edit it.
Confirm the reported code matches react-doctor/no-srcset-without-sizes. 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
<img
srcSet="hero-640.jpg 640w, hero-1280.jpg 1280w"
alt=""
/>Corrected pattern
<img
srcSet="hero-640.jpg 640w, hero-1280.jpg 1280w"
sizes="(min-width: 60rem) 50vw, 100vw"
alt=""
/>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
Reference transformation:Before:react-doctor/no-srcset-without-sizes diagnostic in the current repository.
Required change:
- Add a sizes attribute that describes the image's rendered width at each responsive breakpoint.<img
srcSet="hero-640.jpg 640w, hero-1280.jpg 1280w"
alt=""
/><img
srcSet="hero-640.jpg 640w, hero-1280.jpg 1280w"
sizes="(min-width: 60rem) 50vw, 100vw"
alt=""
/>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.
- Preserve resource ownership and cleanup. Do not move work into a hotter render or frame path.
- 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:
react.
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.Related rules
More Performance rules from the rules reference:
react-doctor/no-sync-xhr: Synchronous XMLHttpRequestreact-doctor/no-tailwind-layout-transition: Animating a layout propertyreact-doctor/no-transition-all: List specific properties: `transition: "opacity 200ms, transform 200ms"` — or in Tailwind use `transition-colors`, `transition-opacity`, or `transition-transform`react-doctor/no-unbounded-animation-frame-loop: Animation frame loop has no stop pathreact-doctor/no-undeferred-third-party: Use `next/script` with `strategy="lazyOnload"` or add the `defer` attribute