`react-doctor/no-fetch-response-used-without-status-check`

fetch Response consumed without status check

Category: Bugs
Severity: warn
Source: oxlint-plugin-react-doctor
Framework: global
Enabled when: always
Tags: test-noise
Default: Enabled

Validate the diagnostic

Confirm the reported code matches this rule before you edit it.

Confirm the reported code matches react-doctor/no-fetch-response-used-without-status-check. 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

const loadProfile = async () => {
  const response = await fetch("/api/profile");
  return response.json();
};

Corrected pattern

const loadProfile = async () => {
  const response = await fetch("/api/profile");
  if (!response.ok) {
    throw new Error(`Request failed: ${response.status}`);
  }
  return response.json();
};

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/no-fetch-response-used-without-status-check diagnostic in the current repository. Required change: - Check response.ok (or response.status) before consuming a fetch Response with .json()/.text()/.blob(). fetch resolves on HTTP 4xx/5xx, so an unchecked response parses the error body as success or crashes on an always-truthy guard.

Reference transformation:Before:

const loadProfile = async () => {
  const response = await fetch("/api/profile");
  return response.json();
};

After:

const loadProfile = async () => {
  const response = await fetch("/api/profile");
  if (!response.ok) {
    throw new Error(`Request failed: ${response.status}`);
  }
  return response.json();
};

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/no-fill-map-element-as-key: fill().map() first param is the element, not the index
react-doctor/no-find-dom-node: Use refs (useRef/createRef) to access DOM nodes instead of the removed findDOMNode API.
react-doctor/no-fixed-inside-transformed-ancestor: Fixed element is scoped by a transformed ancestor
react-doctor/no-floating-then-in-jsx-handler: Floating .then in a JSX event handler
react-doctor/no-hydration-branch-on-browser-global: Render the same initial branch on the server and client instead of branching on a browser global during hydration.

react-doctor/no-fetch-response-used-without-status-check