Documentation
Hono export availability is verification-based. A pattern enables the Hono action only after its generated server project passes the portability checks required for that pattern.
Current runtime target
| Capability | Status |
|---|---|
Hono on Node.js >=24 | Supported |
API routes using Web Request and Response | Supported when verified |
| AI SDK streaming responses | Supported when verified |
| Next.js or React UI inside the Hono archive | Not included |
| Cloudflare Workers | Not claimed |
| Bun or Deno | Not claimed |
| Edge-runtime compatibility | Not claimed |
| Automatic export of preview auth and rate limits | Not included |
Hono can run on several JavaScript runtimes, but these generated projects use
@hono/node-server, Node.js APIs, and a Node-specific dependency set. Do not
change the runtime based only on Hono's general portability claims.
Why some patterns do not show Hono
The exporter starts from each declared API route and follows its local imports to build a standalone server closure. A pattern can be withheld when that closure cannot be packaged and verified safely, for example because it has:
- an undeclared environment variable
- an unsupported or unpinned package dependency
- a browser, React, or Next.js server-only import in the API closure
- a required file that is not registered with the pattern
- an unsafe output path or filename collision
- a source or payload size beyond export limits
- behavior that has not passed the Hono verification suite
An unavailable Hono action does not mean the pattern is broken in Next.js. It means the standalone Hono artifact is not currently offered for that pattern.
What remains unchanged
The exporter mounts the existing route handler instead of translating its AI logic into a new framework-specific implementation. As a result:
- request and response shapes stay aligned with the original route
- AI SDK streams remain Web-standard responses
- the pattern's server source remains recognizable
- retained Next.js route configuration exports may be present but are ignored by Hono
The React UI is a separate concern. You can keep it in a Next.js app and point its transport at the Hono origin by following Connect a Frontend.
Security boundary
The exported closure does not automatically include controls that live in the aisdkagents.com preview wrapper, including product entitlement checks. Use the generated README's authentication and rate-limit declarations to decide what must be added before deployment.
consumer-required and none are not production-ready security controls. See
Production Deployment for the hardening checklist.
Avoid unsupported assumptions
- Do not expect a Hono archive to render the pattern UI.
- Do not deploy it to Workers, Bun, Deno, or an edge runtime without doing your own dependency and protocol verification.
- Do not assume a Next.js
maxDurationvalue controls the Hono service. - Do not assume preview authentication, rate limits, or proxy behavior were copied into the export.
- Do not manually copy a hidden or disabled Hono action and treat it as verified.
ai sdk patterns.