api-client

Copy the createApiClient helper into your app and pass it your urls() patterns value plus the generated route map from rango generate. It returns a client where each route name exposes get, post, put, patch, and delete methods with typed params and responses.

Rango response routes already infer response types from the handler via RouteResponse. The createApiClient helper reuses that inference through type-only imports, so return types are resolved at compile time with no codegen or runtime dependency.

Yes. The helper imports only types from @rangojs/router, which are erased at build time, and builds URLs itself instead of using the server-only createReverse. It runs anywhere fetch is available: browser, worker, or server.

No. Only path params are route-typed via ExtractParams. Search is a generic Record of string, number, or boolean, and body is unknown serialized to JSON. Typed input requires a declared schema layer, which is intentionally out of scope.

Non-2xx responses throw an ApiError carrying the HTTP status and the parsed RFC 9457 ProblemDetails body. You can catch it, check err.status, and read err.problem.code or err.problem.detail with full typing.

No. The client is TypeScript-only and needs your route types. External consumers in any language use the plain wire directly: bare JSON on success and application/problem+json on error, with no client required.