honojs/hono — drift 6.7/10

6.7/10

Notable drift

honojs/hono★ 30,733TypeScript

The documentation covers Hono's high-level features and use cases well, but the primary mismatch is that the docs do not reference the `hc` (Hono Client) function or RPC capabilities in the getting started section or feature list, despite it being prominently exported and mentioned in the DX section. The docs also lack detail on several adapter exports and types that are available in the code.

0 high5 medium0 low

Open issue with all findings ↗

Files analyzed

115

API symbols

Doc pages

15.3s

Analyzed in

10%

API coverage — Poorly documented

11 of 115 exported symbols mentioned in docs

12 source files inspected · claude-haiku-4-5-20251001 · Jun 1, 2026

5 mismatches found

Hono Client `hc` function mentioned in docs but not listed in main exports documentation

src/client/client.ts

medium

In the code

export const hc<T extends Hono<any, any, any>, Prefix extends string = string> = (baseUrl: Prefix, options?: ClientRequestOptions) => …  // src/client/client.ts L133

In the docs

And, the Validator and Hono Client `hc` enable the RPC mode. In RPC mode, you can use your favorite validator such as Zod and easily share server-side API specs with the client and build type-safe applications.

The documentation mentions the `hc` client function in the Developer Experience section but provides no usage examples, import path, or guidance on how to use it. This is a critical client-side tool for RPC mode that developers would need to import from 'hono/client' and its usage is underexplained relative to its importance.

Suggested fix

Add a code example in the DX or RPC mode section showing: `import { hc } from 'hono/client'` and basic usage like `const client = hc('http://api.example.com')` with explanation of how it enables type-safe client calls.

JSX exports from hono/jsx not mentioned in main documentation

src/jsx/index.ts

medium

In the code

export { jsx }  // L36
export { memo }  // L36
export { Fragment }  // L36
export { ErrorBoundary }  // L36
export { createContext }  // L36
export { useState }  // L36
export { useEffect }  // L36
... and 25+ other React-like exports from src/jsx/index.ts

In the docs

[JSX](https://hono.dev/docs/guides/jsx)

The documentation mentions JSX in the middleware list with a link, but does not document the full set of React-like hooks and utilities exported from 'hono/jsx' (useState, useEffect, useCallback, useContext, useMemo, ErrorBoundary, etc.). Developers looking for React patterns in Hono would not know these are available without consulting the JSX guide separately.

Suggested fix

Ensure the JSX guide documentation comprehensively lists all exported hooks and components available from 'hono/jsx', including useState, useEffect, useCallback, useContext, useMemo, ErrorBoundary, Fragment, memo, and other React-compat APIs.

Validator exports not explained in documentation

src/validator/index.ts

medium

In the code

export { validator } from './validator'  // src/validator/index.ts L6
export { ValidationFunction } from './validator'  // L7
export { InferInput } from './utils'  // L8

In the docs

And, the Validator and Hono Client `hc` enable the RPC mode. In RPC mode, you can use your favorite validator such as Zod and easily share server-side API specs with the client and build type-safe applications.

The documentation mentions 'Validator' in the context of RPC mode but does not explain how to import or use the `validator` middleware function, nor does it document the `ValidationFunction` type or `InferInput` utility that are exported from 'hono/validator'.

Suggested fix

Add a code example showing: `import { validator } from 'hono/validator'` and demonstrate basic usage with a schema validator (e.g., Zod), explaining how `ValidationFunction` and `InferInput` work.

Adapter exports not documented in main features section

src/adapter/aws-lambda/index.ts

medium

In the code

export { handle } from './handler'  // src/adapter/aws-lambda/index.ts L6
export { streamHandle } from './handler'  // L6
export { upgradeWebSocket } from './websocket'  // src/adapter/bun/index.ts L8
export { getConnInfo } from './conninfo'  // L10
... multiple adapter-specific exports across various adapters

In the docs

And by using [a Node.js adapter](https://github.com/honojs/node-server), Hono works on Node.js. See [more information about Web Standards](https://hono.dev/docs/concepts/web-standard).

The documentation lists platforms (Cloudflare Workers, Deno, Bun, AWS Lambda, etc.) in the Web Standards section but does not provide detailed export listings or usage examples for adapter-specific functions like `handle`, `streamHandle`, `upgradeWebSocket`, `getConnInfo`, `serveStatic`, or `toSSG`. Developers need to know what is available per adapter.

Suggested fix

Create or update adapter documentation pages (AWS Lambda, Bun, Deno, Cloudflare Pages/Workers, Lambda@Edge) to list their exported functions and types with brief descriptions and import paths (e.g., `import { handle } from 'hono/aws-lambda'`).

parseResponse and DetailedError from hc not mentioned in docs

src/client/index.ts

medium

In the code

export { parseResponse } from './utils'  // src/client/index.ts L7
export { DetailedError } from './utils'  // L7

In the docs

(not documented)

The Hono client exports `parseResponse` utility and `DetailedError` exception class for error handling in RPC mode, but these are not documented. Developers using the `hc` client would not know how to properly handle errors or parse responses.

Suggested fix

Document `parseResponse` and `DetailedError` in the Hono Client guide, explaining when and how to use each for error handling and response parsing.

Re-analyze →Check a different repo