react-doctor/nextjs-no-default-export-in-route-handler
Remove the default export from this route.ts and export the handler as a named HTTP method instead: export async function GET(request: Request) { ... }
- 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
- 58 (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 when the file path matches both APP_DIRECTORY_PATTERN (/app/) and ROUTE_HANDLER_FILE_PATTERN (/route.{ts,tsx,js,jsx,mts,mjs}), and the file has either an ExportDefaultDeclaration (export default ...) or an ExportNamedDeclaration whose specifier is exported as default (export { handler as default }): AND the program does NOT already export a named HTTP method. The suppressing check programHasNamedHttpMethodExport scans for any export named GET/POST/PUT/PATCH/DELETE/OPTIONS/HEAD via a named function declaration, a variable declaration, or an export specifier, so a default export coexisting with a real named method export will not fire.
Suppress when: confirm only if no named HTTP method export exists in the SAME file: if the route already exports e.g. GET or POST as a named symbol the default export is dead but harmless and is correctly not flagged; also suppress for any file not actually named route.* under app/ (a pages/ API route, a non-route module, or a barrel/re-export file that is not itself the route handler), since the gate is purely the filename and never the file's location relative to a route.
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.
Next.js App Router only invokes named HTTP method exports from route.ts and silently ignores the default export, so the endpoint never runs. Delete the default export and re-export the handler under the HTTP verb it serves: replace export default async function handler(request: Request) {...} with export async function GET(request: Request) {...} (or POST/PUT/PATCH/DELETE/OPTIONS/HEAD as appropriate); if the function handles multiple verbs, split it into one named export per method. See https://nextjs.org/docs/app/api-reference/file-conventions/route
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-default-export-in-route-handler diagnostic in the current repository.
Required change:
- Next.js App Router only invokes named HTTP method exports from route.ts and silently ignores the default export, so the endpoint never runs. Delete the default export and re-export the handler under the HTTP verb it serves: replace export default async function handler(request: Request) {...} with export async function GET(request: Request) {...} (or POST/PUT/PATCH/DELETE/OPTIONS/HEAD as appropriate); if the function handles multiple verbs, split it into one named export per method. See https://nextjs.org/docs/app/api-reference/file-conventions/route.
Validation before editing:
Fires only when the file path matches both APP_DIRECTORY_PATTERN (/app/) and ROUTE_HANDLER_FILE_PATTERN (/route.{ts,tsx,js,jsx,mts,mjs}), and the file has either an ExportDefaultDeclaration (export default ...) or an ExportNamedDeclaration whose specifier is exported as default (export { handler as default }): AND the program does NOT already export a named HTTP method. The suppressing check programHasNamedHttpMethodExport scans for any export named GET/POST/PUT/PATCH/DELETE/OPTIONS/HEAD via a named function declaration, a variable declaration, or an export specifier, so a default export coexisting with a real named method export will not fire.
Suppress when: confirm only if no named HTTP method export exists in the SAME file: if the route already exports e.g. GET or POST as a named symbol the default export is dead but harmless and is correctly not flagged; also suppress for any file not actually named route.* under app/ (a pages/ API route, a non-route module, or a barrel/re-export file that is not itself the route handler), since the gate is purely the filename and never the file's location relative to a route.
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.