hono-third-party

Install a validator package such as @hono/zod-validator and apply it as middleware with the shared contract validator(target, schema, hook). Access validated data in the handler via c.req.valid('json') or the matching target like 'query' or 'param'.

Choose Zod for the widest ecosystem familiarity, Valibot for a modular tree-shakable build, and TypeBox when JSON Schema must be the source of truth. All share the same validator(target, schema, hook) signature, so switching libraries requires minimal changes.

Pick the @hono package matching your provider: @hono/auth-js for Auth.js, @hono/clerk-auth for Clerk, @hono/firebase-auth for Firebase ID tokens, @hono/oidc-auth for OpenID Connect, or @hono/oauth-providers for social logins like Google and GitHub. Each injects the session into the Hono context.

Yes, most @hono packages are edge-compatible, including Firebase Auth, Cloudflare Access, and the esbuild transpiler via its Wasm build. Some packages have runtime notes, such as OpenTelemetry metrics being limited on Workers and node-ws being deprecated in favor of @hono/node-server.

Use @hono/zod-openapi's OpenAPIHono class with createRoute to define validated routes, then call app.doc('/doc', {...}) to serve the OpenAPI definition. Pair it with @hono/swagger-ui to render interactive documentation at a route like /ui.

Avoid @hono/bun-compress because it is deprecated; Bun now supports CompressionStream natively. Replace it with Hono's built-in hono/compress middleware, which exposes the identical API with no other code changes required.