`react-doctor/react-router-no-middleware-response-body-consumption`

Middleware consumes the outgoing response body

Category: Bugs
Severity: warn
Source: oxlint-plugin-react-doctor
Framework: global
Enabled when: react-router:7.9, react-router-framework
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/react-router-no-middleware-response-body-consumption. 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

export const middleware = [async (_, next) => {
  const response = await next();
  log(await response.text());
  return response;
}];

Corrected pattern

export const middleware = [async (_, next) => {
  const response = await next();
  log(await response.clone().text());
  return response;
}];

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/react-router-no-middleware-response-body-consumption diagnostic in the current repository. Required change: - Inspect or change response headers and status without consuming the body returned by next().

Reference transformation:Before:

export const middleware = [async (_, next) => {
  const response = await next();
  log(await response.text());
  return response;
}];

After:

export const middleware = [async (_, next) => {
  const response = await next();
  log(await response.clone().text());
  return response;
}];

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. - Confirm this rule is enabled for the project: react-router:7.9, react-router-framework. 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/react-router-no-multiple-blockers: Multiple blockers in one component
react-doctor/react-router-no-multiple-middleware-next: Middleware continuation called twice
react-doctor/react-router-no-multiple-set-search-params-in-tick: Search params updated multiple times
react-doctor/react-router-no-navigate-in-render: navigate() called during render
react-doctor/react-router-no-nested-router: Router nested inside another router

react-doctor/react-router-no-middleware-response-body-consumption