hono-rpc

To generate a type-safe API client for a Hono application, export your server's AppType and use the built-in hc client to make fully type-checked API calls. This approach uses TypeScript inference to derive client types directly from server routes.

Yes, you can use Zod validation in a Hono RPC setup to achieve end-to-end type safety. The client automatically infers types for JSON bodies, query parameters, and headers validated by Zod on the server, preventing runtime errors.

The best way to achieve end-to-end type safety without codegen is using TypeScript's inference system. By exporting your Hono server's AppType, the client automatically derives route types, eliminating manual code generation and reducing integration errors.

Yes, Hono's RPC client supports path parameters and form data. The type-safe client inference automatically handles path parameters, query parameters, JSON bodies, form data, and headers, ensuring all client API calls are strictly type-checked.

You need to export your server's AppType for Hono RPC because the client relies on TypeScript inference to automatically derive types from your server routes. Without exporting the AppType, the hc client cannot access the route definitions to provide type checking.