Issue with Type Error in Next.js Adapter Sample Code

[FlatMapIO]

When copying the sample code from https://orpc.unnoq.com/docs/adapters/next#next-js-adapter, I encountered a type error. The context requires a header with the type nodejs IncomingRequestHeader.

async function handleRequest(request: Request) {
  const { response } = await handler.handle(request, {
    prefix: '/rpc',
    context: {
       // type error
    }, 
  })

  return response ?? new Response('Not found', { status: 404 })
}

I have two questions for clarification:

1. Since we're using the web standard API, could you explain why there's a Node.js-specific header requirement?
2. The first argument of handle is already a request object—could you clarify why the header needs to be passed again in the context?

Would appreciate any guidance on resolving this or adjusting the example for better alignment with web standards. Thanks!

[dosubot]

Hi @FlatMapIO! I'm Dosu and I’m helping the orpc team.

The Node.js-specific IncomingRequestHeader type requirement in the context looks like a legacy or documentation artifact—recent ORPC Next.js examples and the playground just pass an empty context object or use web standard headers, not Node.js types. The codebase doesn't enforce Node.js headers for the Next.js adapter; instead, it handles requests using the standard Request object and context is optional unless your middleware or handlers specifically need headers for things like authentication or logging. If you do need headers, you can pass them in the context using the web standard Headers API (for example, via Next.js's headers() helper) rather than Node.js types citation citation.

The reason the context sometimes includes headers is to make them available to downstream middleware or business logic, but it's not required if your handlers don't use them—especially since the request object already contains all header data. If you hit a type error, try passing an empty object as context, or if your contract expects headers, convert the web standard headers to a plain object (e.g., Object.fromEntries(request.headers.entries())).

Make sure your code and types match the latest ORPC playground and docs, as the @orpc/next package has been removed and the adapter is evolving for better web standards alignment citation. If you have custom middleware that expects Node.js headers, consider updating it to accept the web standard Headers instead.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[FlatMapIO]

Thank you for your response. I know where the problem is. The example router provided in the get starter page contains the following code:

export const createPlanet = os
  .$context<{ headers: IncomingHttpHeaders }>()

I understand the problem, it has nothing to do with orpc. Close this issue.