hono-routing

Type-safe API routes with Hono use routing patterns combined with request validators like Zod or Valibot. Define routes with typed handlers, apply validators to enforce request shape, and leverage TypeScript's type inference to guarantee compile-time safety. The Skill covers middleware composition, context extension, and error handling patterns across Node.js, Deno, Bun, and Cloudflare Workers.

Yes. Hono supports RPC patterns through typed route exports that expose your server API to the client with full type inference. Define routes on the server, export their types, and consume them on the client side with IDE autocomplete and type checking. This eliminates the need to manually synchronize client and server contracts.

Request validation in Hono uses validator middleware like Zod, Valibot, Typia, or ArkType. Apply validators to your route handlers via c.req.valid() hooks; Hono parses and validates the request body, query, or headers. Failed validations trigger structured error handling through HTTPException and onError hooks for consistent responses.

Middleware chains in Hono use await next() to pass control between layers. Stack middleware before route handlers to manage authentication, logging, or context setup. Each middleware executes before the route, and you can modify context or request state. The Skill covers composition patterns for complex pipelines.

Hono routing patterns work across Cloudflare Workers, Deno, Bun, and Node.js. The same routing, validation, middleware, and RPC patterns apply to all environments. Deploy type-safe routes to serverless platforms or traditional servers without rewriting validation or error handling logic.

Hono error handling uses HTTPException for structured error responses and onError hooks for global error processing. Throw HTTPException with a status code and message from any route or middleware; onError catches and formats responses. Combine this with typed context and validation errors for uniform error contracts.