export type AfterGenerateHook = (result: ToSSGResult) => void | Promise<void>

afterGenerateHook: (result, fsModule, options) => { ... }

The documentation example shows the afterGenerateHook receiving three parameters (result, fsModule, options), but the actual type definition only accepts one parameter (result). A developer following the docs example would pass incorrect arguments.

Update the documentation example to remove the fsModule and options parameters from the afterGenerateHook signature, or update the code type definition to match the documented signature if those parameters are actually needed.

export { parseResponse, DetailedError, Fetch, ClientRequest, ClientResponse, ApplyGlobalResponse, PickResponseByStatusCode } from 'hono/client'

(not documented)

The code exports several client-related utilities (parseResponse, DetailedError) and types (Fetch, ClientRequest, ClientResponse, ApplyGlobalResponse, PickResponseByStatusCode) that are not mentioned in the documentation. Developers using the hc client may need to use these but have no guidance.

Add documentation for these client exports, particularly parseResponse and DetailedError, which are utility functions developers might need to use.

export { jsx, memo, Fragment, ErrorBoundary, createContext, useContext, useState, useEffect, useRef, useCallback, useReducer, useId, useDebugValue, use, startTransition, useTransition, useDeferredValue, startViewTransition, useViewTransition, useMemo, useLayoutEffect, useInsertionEffect, createRef, forwardRef, useImperativeHandle, useSyncExternalStore, useActionState, useOptimistic, Suspense, Children, DOMAttributes } from 'hono/jsx'

(not documented)

The code exports many React-like APIs from hono/jsx (such as useActionState, useOptimistic, startViewTransition, useViewTransition, useLayoutEffect, useInsertionEffect, useSyncExternalStore, useDebugValue, etc.), but these are not individually documented or listed. The JSX guide exists but does not enumerate these specific exported functions.

Add a section to the JSX documentation listing all exported functions and hooks from hono/jsx with brief descriptions of each.

export { ValidationFunction, InferInput } from 'hono/validator'

(not documented)

The code exports ValidationFunction and InferInput types from hono/validator, but the validator documentation does not mention these types. Developers implementing custom validators may need to reference ValidationFunction but have no documentation for it.

Add documentation for ValidationFunction and InferInput types in the validator section, explaining when and how to use them.

export { bunFileSystemModule, BunWebSocketData, BunWebSocketHandler } from 'hono/bun'

(not documented)

The code exports BunWebSocketData, BunWebSocketHandler, and bunFileSystemModule from the Bun adapter, but these types and utilities are not documented. Developers working with WebSockets on Bun may need guidance on these types.

Add documentation for Bun adapter WebSocket types and the bunFileSystemModule export.

export { defaultIsContentTypeBinary, APIGatewayProxyResult, LambdaEvent, ApiGatewayRequestContext, ApiGatewayRequestContextV2, ALBRequestContext, LambdaContext } from 'hono/aws-lambda'

(not documented)

The code exports several types and functions related to AWS Lambda (defaultIsContentTypeBinary, APIGatewayProxyResult, LambdaEvent, etc.) but these are not documented. Users trying to customize Lambda deployments may need these exports.

Add documentation for AWS Lambda adapter exports, particularly the types and defaultIsContentTypeBinary function.

export { EventContext } from 'hono/cloudflare-pages'

(not documented)

The code exports EventContext type from the Cloudflare Pages adapter, but this is not documented. The type may be useful for users working with Cloudflare Pages but have no guidance.

Add documentation for the EventContext type exported from hono/cloudflare-pages.

export { Callback, CloudFrontConfig, CloudFrontRequest, CloudFrontResponse, CloudFrontEdgeEvent } from 'hono/lambda-edge'

(not documented)

The code exports several Lambda@Edge-specific types (Callback, CloudFrontConfig, CloudFrontRequest, CloudFrontResponse, CloudFrontEdgeEvent) but these are not documented. Users working with Lambda@Edge may need to reference these types.

Add documentation for Lambda@Edge types, particularly CloudFrontConfig, CloudFrontRequest, and CloudFrontResponse.