Repository navigation

[pages] incorrect API route validation #83067

Closed

Assignees

Labels

opened

on Aug 26, 2025

In the source code, we export

export type NextApiHandler<T = any> = (
  req: NextApiRequest,
  res: NextApiResponse<T>
) => unknown | Promise<unknown>

But the validator expects

(req: any, res: any) => Promise<Response | void> | Response | void

This was a mistake on my part -- the first type is accurate and the second is not.

Referenced by @WilliamIPark, @ecl1ps, @MadaShindeInai, @HimanshuKumarDutt094, and @soulchild in #82877 (tagging so you can follow this issue)

bgub
added the
Bug
issue type on Aug 26, 2025
github-actions
added
TypeScriptRelated to types with Next.js.
on Aug 26, 2025
github-actions
closed this as completed on Aug 26, 2025
github-actions
added
invalid linkThe issue was auto-closed due to a missing/invalid reproduction link. A new issue should be opened.
on Aug 26, 2025
github-actions
locked and limited conversation to collaborators on Aug 26, 2025
bgub
removed
invalid linkThe issue was auto-closed due to a missing/invalid reproduction link. A new issue should be opened.
on Aug 26, 2025
bgub
reopened this on Aug 26, 2025
bgub
self-assigned this
on Aug 26, 2025
vercel
deleted a comment from github-actions on Aug 26, 2025
bgub
changed the title ~~[-][pages] API route validation is too strict[/-]~~ [+][pages] incorrect API route validation[/+] on Aug 26, 2025
bgub
closed this as completedin #83069 on Aug 27, 2025
bgub
added 2 commits that reference this issue on Aug 27, 2025
fix: validation return types of pages API routes (#83069)
2880238
fix: validation return types of pages API routes (#83069)
d5add9c
bgub
added a commit that references this issue on Sep 8, 2025
fix: validation return types of pages API routes (vercel#83069)
d6c5fcb

to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

bgub

Labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests