hono

Create a Hono app instance and define routes with methods like app.get, app.post, and app.delete, returning responses via c.json or c.text. Organize handlers into sub-routers and mount them with app.route for larger applications.

Use the zValidator middleware from @hono/zod-validator with a Zod schema, then access the parsed data through c.req.valid. This gives fully typed request bodies, query parameters, and route params in your handlers.

Yes, Hono runs on Cloudflare Workers, Deno, Bun, Node.js, AWS Lambda, and any WinterCG-compatible runtime with the same code. Platform bindings like D1 databases are accessed through c.env on Workers, while Node.js uses process.env.

The hc client consumes exported route types from your Hono server to provide end-to-end type safety over fetch, similar to tRPC. It offers autocomplete on routes, params, and responses when frontend and backend share a repository.

Handlers must explicitly return a response, such as return c.json(data), rather than just calling c.json without returning it. Also ensure middleware calls await next() before any post-response logic.