`react-doctor/nextjs-async-dynamic-api-not-awaited`

Synchronous Next.js request API access

Category: Bugs
Severity: error
Source: oxlint-plugin-react-doctor
Framework: nextjs
Enabled when: nextjs:15
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/nextjs-async-dynamic-api-not-awaited. 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

import { cookies } from "next/headers";

export const readTheme = () => {
  return cookies().get("theme")?.value;
};

Corrected pattern

import { cookies } from "next/headers";

export const readTheme = async () => {
  return (await cookies()).get("theme")?.value;
};

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/nextjs-async-dynamic-api-not-awaited diagnostic in the current repository. Required change: - Await cookies(), headers(), draftMode(), and async route params or searchParams, or unwrap their promises with React use(), before reading properties.

Reference transformation:Before:

import { cookies } from "next/headers";

export const readTheme = () => {
  return cookies().get("theme")?.value;
};

After:

import { cookies } from "next/headers";

export const readTheme = async () => {
  return (await cookies()).get("theme")?.value;
};

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: nextjs:15. 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/nextjs-error-boundary-missing-use-client: Add `'use client'` as the first statement of error.tsx / global-error.tsx so the error boundary becomes a Client Component.
react-doctor/nextjs-global-error-missing-html-body: Wrap the global-error UI in `<html><body>...</body></html>` because the root layout unmounts when global-error renders
react-doctor/nextjs-image-missing-sizes: Add sizes for responsive behavior: `sizes="(max-width: 768px) 100vw, 50vw"` matching your layout breakpoints
react-doctor/nextjs-inline-script-missing-id: Add `id="descriptive-name"` so Next.js can track, deduplicate, and re-execute the script correctly
react-doctor/nextjs-metadata-url-consistency: Canonical and Open Graph URLs disagree

react-doctor/nextjs-async-dynamic-api-not-awaited