--- name: hono-rpc-8e4f1cdcb0eb description: >- Hono RPC shares a Hono server's route types with a typed fetch client (hc), giving end-to-end type safety for REST APIs without code generation or schema files. Use when building a type-safe API with Hono, sharing API types between frontend and backend, validating input with Zod and getting the types on the client, or replacing tRPC with plain REST. Runs on Cloudflare Workers, Deno, Bun and Node.js. license: Apache-2.0 compatibility: "Hono 4.x (@hono/zod-validator 0.9 needs hono >= 4.11.2 and zod 3.25+ or 4), TypeScript with strict mode. Runs on Cloudflare Workers, Deno, Bun, Node.js." metadata: author: terminal-skills version: "1.1.0" category: development repository: https://github.com/honojs/hono tags: "hono, rpc, type-safe, cloudflare-workers, typescript" use-cases: "Build a type-safe REST API with Hono RPC and share types with the frontend, Replace tRPC with Hono RPC for a REST-compatible type-safe API, Create a Cloudflare Workers API with full type inference on the client, Validate API inputs with Zod middleware and propagate types to the client" agents: "claude-code, openai-codex, gemini-cli, cursor" --- # Hono RPC ## Overview Hono RPC links a Hono server and its clients through types. Routes with validators are written on the server, the app's type is exported as `AppType`, and the `hc()` client from `hono/client` then knows every path, method, input and JSON response. The client is a thin wrapper over `fetch`; nothing is generated. Type inference only sees what the chain of route definitions exposes, so most pitfalls below are about keeping that chain intact. ## Instructions ### Install ```bash npm install hono zod @hono/zod-validator npm install @hono/node-server # only when running on Node.js ``` On Bun and Cloudflare Workers `hono` is enough for the server. On Deno import `jsr:@hono/hono`. Set `"strict": true` in the `tsconfig.json` of both server and client (in a monorepo, of every package); without it the inferred types degrade. The validator also works with Standard Schema libraries such as Valibot through `@hono/standard-validator`. ### Define routes and export the type Chain the handlers (`new Hono().get(...).post(...)`) so each call adds to the type, and export `typeof` the final value: ```ts // src/server.ts import { Hono } from "hono"; import { zValidator } from "@hono/zod-validator"; import { z } from "zod"; const createUser = z.object({ name: z.string().min(1), email: z.string().email(), age: z.number().int().positive().optional(), }); const users = new Hono() .get("/", (c) => c.json({ users: [{ id: 1, name: "Maria Lopez", email: "maria@lopez-studio.es" }] })) .get("/:id", (c) => { const id = Number(c.req.param("id")); if (id !== 1) return c.json({ error: "User not found" }, 404); return c.json({ user: { id, name: "Maria Lopez" } }, 200); }) .post("/", zValidator("json", createUser), (c) => { const data = c.req.valid("json"); // typed from the schema return c.json({ user: { id: 2, ...data } }, 201); }) .patch("/:id", zValidator("json", createUser.partial()), (c) => { return c.json({ user: { id: Number(c.req.param("id")), ...c.req.valid("json") } }); }) .delete("/:id", (c) => c.json({ deleted: Number(c.req.param("id")) })); const app = new Hono().route("/users", users); export type AppType = typeof app; export default app; ``` Run it on Node.js with `import { serve } from "@hono/node-server"; serve({ fetch: app.fetch, port: 3000 });`. Bun and Workers use the default export directly. ### Call it from the client ```ts import { hc } from "hono/client"; import type { AppType } from "./server"; // type-only import: no server code ships to the browser const client = hc("http://localhost:3000"); const list = await client.users.$get(); if (list.ok) console.log((await list.json()).users); const created = await client.users.$post({ json: { name: "Tom Becker", email: "tom@becker.dev", age: 30 } }); const one = await client.users[":id"].$get({ param: { id: "1" } }); await client.users[":id"].$patch({ param: { id: "1" }, json: { name: "Tom B." } }); await client.users[":id"].$delete({ param: { id: "1" } }); ``` Path parameters and query values must be passed as strings even when the schema turns them into numbers. `hc` does not URL-encode `param`; wrap values that may contain `/` in `encodeURIComponent`, or declare the route with a regexp such as `/files/:name{.+}`. ### Query, headers, cookies, abort ```ts const search = new Hono().get( "/search", zValidator("query", z.object({ q: z.string().optional(), page: z.coerce.number().default(1) })), (c) => c.json({ results: [], ...c.req.valid("query") }), ); type SearchApp = typeof search; const client = hc("http://localhost:3000", { headers: { Authorization: `Bearer ${process.env.API_TOKEN}` }, // sent with every call init: { credentials: "include" }, // send cookies }); const res = await client.search.$get({ query: { q: "hono", page: "2" } }); const withId = await client.search.$get({ query: { q: "x" } }, { headers: { "X-Request-ID": crypto.randomUUID() } }); ``` Per-call options (second argument) accept `headers` and `init` (a `RequestInit`, for example `{ signal }` to abort; `init` wins over other options). Other validator targets are `form`, `param`, `header` and `cookie`; file uploads go through `form` with a `File`. ### Status codes and errors Give `c.json()` an explicit status so the client can narrow on it. Do not use `c.notFound()` in an RPC route: its body is untyped and the client sees `unknown`. Return `c.json({ error: "..." }, 404)` instead. ```ts const res = await client.users[":id"].$get({ param: { id: "999" } }); if (res.status === 404) console.error((await res.json()).error); if (res.ok) console.log((await res.json()).user); ``` Errors thrown with `HTTPException` or returned by `app.onError()` and global middleware are not part of the inferred types. Wrap the type with `ApplyGlobalResponse` from `hono/client` to add them: `hc>(url)`. `parseResponse` from `hono/client` parses the body by content type and throws a `DetailedError` when the response is not ok, which suits data-fetching hooks: ```ts import { parseResponse } from "hono/client"; const { users } = await parseResponse(client.users.$get()); ``` ### Infer request and response types ```ts import type { InferRequestType, InferResponseType } from "hono/client"; const $post = client.users.$post; type CreateUserBody = InferRequestType["json"]; type CreateUserOk = InferResponseType; // pick one status code ``` ### Larger apps and monorepos Build each sub-router as a chained `new Hono()`, mount with `.route()`, and export the type of the mounted result. Handlers registered separately (`app.get(...)` on its own line, or sub-routers that are not chained) are invisible to the client. A handler that returns a bare `.then()` chain loses its response type; make it `async` and return `c.json(...)`. In a monorepo, re-export `AppType` from the API package and import it type-only in the web package, with the same `hono` version on both sides (a mismatch breaks inference). With many routes the IDE slows down; compile the client type once: ```ts // packages/api/src/client.ts import { hc, type ClientRequestOptions } from "hono/client"; import type { app } from "./app"; type App = typeof app; const probe = hc(""); export type Client = typeof probe; export const hcWithType = (url: string, options?: ClientRequestOptions): Client => hc(url, options); ``` Then build the API package with `tsc` and use `hcWithType` in the frontend. Splitting one client per sub-app (`hc("/authors")` with `type AuthorsApp = typeof authorsApp`) also helps. ### Cloudflare Workers ```ts // src/index.ts import { Hono } from "hono"; import { cors } from "hono/cors"; import { zValidator } from "@hono/zod-validator"; import { z } from "zod"; const app = new Hono<{ Bindings: { DB: D1Database } }>() .use("/api/*", cors({ origin: ["https://shop.example.org"], allowMethods: ["GET", "POST"] })) .get("/api/items", async (c) => { const { results } = await c.env.DB.prepare("SELECT id, name, price FROM items").all(); return c.json({ items: results }); }) .post("/api/items", zValidator("json", z.object({ name: z.string(), price: z.number() })), async (c) => { const { name, price } = c.req.valid("json"); await c.env.DB.prepare("INSERT INTO items (name, price) VALUES (?, ?)").bind(name, price).run(); return c.json({ ok: true }, 201); }); export type AppType = typeof app; export default app; ``` Declare the D1 binding in `wrangler.jsonc` (or `wrangler.toml`) and generate binding types with `npx wrangler types`; deploy with `npx wrangler deploy`. ## Examples **"Give my React app typed calls to the Hono API."** Export `AppType` from the server, add the API package as a dependency of the web app, then in `web/src/api.ts` write `export const api = hc(import.meta.env.VITE_API_URL);`. In a query function `const res = await api.users.$get(); return res.json();` gives `{ users: ... }` typed. Renaming a field on the server turns the affected client lines red at compile time. **"Why is `res.json()` unknown?"** Check, in order: the route was added in the chain that is exported as `AppType`; the handler returns `c.json(...)` (not `c.notFound()`, `c.text()` or a raw `Response`); the status is explicit if the response has several; `strict` is on; server and client resolve the same `hono` version. ## Guidelines - Export `AppType` as `typeof app` of the final chained, mounted app, never an interface or an app built from unchained calls. - Validate every input with `zValidator` (json, form, query, param, header, cookie); the schema is also what types the client. - Query and path values are strings on the wire; use `z.coerce.number()` on the server and pass strings from the client. - Import `AppType` with `import type` so the server never enters the client bundle. - Never put secrets in client-side `hc` headers; the browser exposes them. - RPC types cover only JSON-style responses from `c.json()`; for streams, redirects or files use plain `fetch` or `client.path.$url()`. --- Source attribution: terminal-skills Original project: https://github.com/TerminalSkills/skills/blob/8a9852d489f274538be9bf1c9121aeb403750b1c/skills/hono-rpc/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Dave AI. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS Copyright 2025 Terminal Skills Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Dave AI resource metadata Creator / publisher: terminal-skills Original project: https://github.com/TerminalSkills/skills/blob/8a9852d489f274538be9bf1c9121aeb403750b1c/skills/hono-rpc/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering Roles: Backend Developer, Data Engineer, ML / AI Engineer Specialties: API, Backend Tools: Cloudflare Workers, Deno, Bun, Node.Js Country applicability: Country not specified Classification basis: Source category, role and specialization labels Instruction SHA-256: 0c492a83dc8fbece445529a9be2d187e96f8a0ec0d33a960e8613100d4ed1375