react-doctor/nextjs-no-head-import
Use the Metadata API instead: `export const metadata = { title: '...' }` or `export async function generateMetadata()`
- Status
- Active
- Category
- Next.js
- Assessment
- Evidence-required risk
- Required evidence
- source code
- Default configuration
- Enabled
- Default severity
- error
Show technical metadata
- Scope
- Next.js
- Active when
- framework=nextjs and capabilities=nextjs
- Requirements
- nextjs
- Tags
- test-noise
- Priority
- 67 (P2)
- 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.
Triggers only when import ... from 'next/head' appears in a file whose path contains /app/. Pages Router files (under /pages/) may legitimately use next/head and are not flagged. False positive if /app/ appears coincidentally in a path that isn't actually the App Router (e.g. a monorepo named 'app').
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.
Delete the next/head import and <Head> JSX. Export metadata (static) or generateMetadata (dynamic) from the page or layout. Use file conventions like icon.tsx, opengraph-image.tsx, robots.ts, and sitemap.ts for non-meta tags; return arbitrary <meta> via generateMetadata. https://nextjs.org/docs/app/getting-started/metadata-and-og-images
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/nextjs-no-head-import diagnostic in the current repository.
Required change:
- Delete the next/head import and <Head> JSX. Export metadata (static) or generateMetadata (dynamic) from the page or layout. Use file conventions like icon.tsx, opengraph-image.tsx, robots.ts, and sitemap.ts for non-meta tags; return arbitrary <meta> via generateMetadata. https://nextjs.org/docs/app/getting-started/metadata-and-og-images.
Validation before editing:
Triggers only when import ... from 'next/head' appears in a file whose path contains /app/. Pages Router files (under /pages/) may legitimately use next/head and are not flagged. False positive if /app/ appears coincidentally in a path that isn't actually the App Router (e.g. a monorepo named 'app').
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.
- 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:
framework=nextjs and capabilities=nextjs.
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.