@unthrown/orpc

---

@unthrown/orpc / server

server

Server

ResultHandler

type ResultHandler<TCurrentContext, TInput, TOutput, TError, TErrorMap> = (opts, input) => 
  | Result<TOutput, TError>
  | Promise<Result<TOutput, TError>>
  | AsyncResult<TOutput, TError>;

Defined in: server.ts:35

A procedure handler that speaks Result: same options as a plain oRPC handler (input, context, errors, …), returning a Result<TOutput, TError> — synchronous, promised, or as an AsyncResult.

Type Parameters

Type Parameter
TCurrentContext extends Context
TInput
TOutput
TError extends AnyORPCError
TErrorMap extends ErrorMap

Parameters

Parameter	Type
opts	ProcedureHandlerOptions<TCurrentContext, TInput, ORPCErrorConstructorMap<TErrorMap>>
input	TInput

Returns

| Result<TOutput, TError> | Promise<Result<TOutput, TError>> | AsyncResult<TOutput, TError>

---

handlerResult()

function handlerResult<TCurrentContext, TInput, TOutput, TError, TErrorMap>(handler): ProcedureHandler<TCurrentContext, TInput, TOutput | TError, ORPCErrorConstructorMap<TErrorMap>>;

Defined in: server.ts:80

Adapt a Result-returning handler into a plain oRPC procedure handler.

Type Parameters

Type Parameter
TCurrentContext extends Context
TInput
TOutput
TError extends AnyORPCError
TErrorMap extends ErrorMap

Parameters

Parameter	Type	Description
handler	ResultHandler<TCurrentContext, TInput, TOutput, TError, TErrorMap>	the Result-speaking handler to adapt.

Returns

ProcedureHandler<TCurrentContext, TInput, TOutput | TError, ORPCErrorConstructorMap<TErrorMap>>

Remarks

The elimination boundary of the server half: Ok becomes the procedure's output; Err (constrained to ORPCError — build one with the injected errors.CODE(...) constructors, or map a domain error via mapErr first) is returned as a value, which oRPC marks inferable so the client sees it fully typed; a Defect rethrows its original cause, which oRPC collapses to INTERNAL_SERVER_ERROR — a bug stays a defect, never a typed error.

Like match handlers, the callback may be async (an edge elimination is exempt from the no-thenable rule): a rejection or throw inside it cannot skip triage, because oRPC's own boundary already treats it as the defect path.

Example

import { handlerResult } from "@unthrown/orpc/server";

const find = os
  .input(z.object({ id: z.string() }))
  .errors({ NOT_FOUND: {} })
  .handler(
    handlerResult(({ input, errors }) =>
      repo.findPlanet(input.id).mapErr(() => errors.NOT_FOUND()),
    ),
  );