hono

Export the chained route's typeof as AppType on the server, then create a client with hc<AppType>(baseUrl). The client gets full autocompletion for paths, methods, inputs, and typed responses without code generation.

Use the built-in validator() middleware with a target like 'json' or 'form', returning a Response to reject invalid input. For schema validation, use @hono/zod-validator or @hono/standard-validator, then read typed data via c.req.valid().

Yes, the same Hono application code runs on Cloudflare Workers, Node.js, Deno, Bun, AWS Lambda, Vercel, and more. Only the entry point differs: export default app for Workers, or use @hono/node-server's serve() for Node.js.

Use the default hono preset (SmartRouter with RegExpRouter) for long-running servers. Use hono/quick when the app re-initializes per request, and hono/tiny (under 14KB) when bundle size is the primary constraint on edge environments.

Path params are inferred only when handlers are defined inline on the route. Extracting handlers into separate controller functions breaks inference; use createFactory().createHandlers() to extract handlers while preserving types.

Throw HTTPException with a status and message for expected errors, and register app.onError() as a catch-all that maps HTTPException to its response and returns a generic 500 otherwise. Do not wrap next() in try/catch since Hono routes thrown errors to onError.