In-process

Use inProcessTransport() when the caller can import a completed implementation safely. The transport dispatches by immutable contract key, passes encoded parameters directly, and executes the same server validation, context, middleware, handler, response, and declared-error lifecycle as other transports.

import { createClient } from '@hulla/api/client'
import { inProcessTransport } from '@hulla/api/in-process'
import { contract } from './contract'
import { implementation } from './implementation'

export const api = createClient(contract, {
  transport: inProcessTransport(implementation),
})

This is a zero-network call, not an HTTP simulation. Native JSON values pass directly instead of being stringified and parsed, so keep type-only JSON declarations JSON-compatible if the same contract also uses HTTP. Codecs still encode and decode their application values.

Because the local client imports the implementation, place it behind a server-only module boundary. Browser code should build a separate client from the same contract with fetchTransport() or another remote transport. The hybrid rendering guide shows safe placements for full-stack frameworks.

Use ordinary functions when no contract lifecycle is needed. In-process transport is useful when a local caller should observe the same validation, middleware, declared statuses, errors, and cancellation behavior as a remote caller.