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
- 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
- 62 (P2)
- Source
- oxlint-plugin-react-doctor
- Rule set
- oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
- Documentation
- Official documentation
Validation prompt
Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.
Fires only on files whose normalized path matches /app/ AND ends in global-error.{tsx,jsx,ts,js,mts,mjs} when the file's JSX is missing an <html> and/or <body> tag: fileContainsJsxElements walks the whole Program for JSXOpeningElements whose JSXIdentifier name is the lowercase literal "html" or "body", and the report names whichever of the two is absent. global-error replaces the unmounted root layout, so it must render its own <html><body>.
Suppress when: the tags exist but the walker missed them because they are not literal lowercase JSX identifiers: e.g. <body> is produced by a wrapper/layout component, spread, or a styled/aliased element (Html from a constant, an uppercase styled-components Body) rather than written inline; also a file that merely re-exports a global-error component defined elsewhere where the JSX lives in the imported module.
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.
Render your own document shell inside the GlobalError component since the root layout is unmounted on a global error: return <html><body><h2>Something went wrong</h2><button onClick={() => reset()}>Try again</button></body></html>, accepting ({ error, reset }) props and keeping the file a Client Component with 'use client' at the top. Both <html> and <body> must be present as literal lowercase tags: inline them rather than relying on a shared layout component. See https://nextjs.org/docs/app/api-reference/file-conventions/error#global-error
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-global-error-missing-html-body diagnostic in the current repository.
Required change:
- Render your own document shell inside the GlobalError component since the root layout is unmounted on a global error: return <html><body><h2>Something went wrong</h2><button onClick={() => reset()}>Try again</button></body></html>, accepting ({ error, reset }) props and keeping the file a Client Component with 'use client' at the top. Both <html> and <body> must be present as literal lowercase tags: inline them rather than relying on a shared layout component. See https://nextjs.org/docs/app/api-reference/file-conventions/error#global-error.
Validation before editing:
Fires only on files whose normalized path matches /app/ AND ends in global-error.{tsx,jsx,ts,js,mts,mjs} when the file's JSX is missing an <html> and/or <body> tag: fileContainsJsxElements walks the whole Program for JSXOpeningElements whose JSXIdentifier name is the lowercase literal "html" or "body", and the report names whichever of the two is absent. global-error replaces the unmounted root layout, so it must render its own <html><body>.
Suppress when: the tags exist but the walker missed them because they are not literal lowercase JSX identifiers: e.g. <body> is produced by a wrapper/layout component, spread, or a styled/aliased element (Html from a constant, an uppercase styled-components Body) rather than written inline; also a file that merely re-exports a global-error component defined elsewhere where the JSX lives in the imported module.
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.