Hono

Why it's ranked here

Most of the value sits in one decision: the request and response types are the platform's own, not a bespoke wrapper. That is why one codebase deploys to edge runtimes and to Node, and why nothing beyond the Web Standard API is pulled in. The router is not hidden either, it is a constructor option, and the default hedges by racing two strategies at registration time. The cost is dense type machinery behind the ergonomics, and a per-runtime adapter for anything the standard does not cover. On a Workers-style runtime this is the sensible default pick.

What's good

Every capability is its own entry point. Authentication, CORS, compression, caching, JWT, static serving and JSX rendering each import separately, so what you skip never reaches the bundle. Error handling has one seam: an app-level handler catches anything a route throws, and exceptions carrying their own response are converted into that response. Sub-applications mounted under a prefix keep their own error handler wrapped around their routes. Request bodies are memoised after the first read, so two middleware layers can both parse a body without the second finding an already drained stream.

Tradeoffs

The generics are the price of the typed client. Handler signatures thread environment, schema, base path and current path through every method, so a mismatch surfaces as a long inference error rather than a plain one. Runtime coverage is real but uneven: each target needs its own adapter, and its own helpers for websockets and connection info, so a feature on one platform is not guaranteed on the next. When mounting a foreign application, the execution context is read inside a try block with an empty catch, so the mounted handler silently receives undefined. No data layer, no auth provider, no jobs.

How to use it well

Reach for it when the server runs on an edge runtime or a serverless function and you want routing, middleware and typed responses without a Node-shaped framework underneath. It suits APIs, webhook receivers and small full-stack apps returning JSON or server-rendered HTML. The typed client pays off when the frontend lives in the same repository. It covers none of the data layer: bring your own database driver, your own migrations, your own session store and your own auth provider. On Node you still supply a separate process entry point to hand incoming requests over.

Observed

License

MIT

Language

TypeScript

Interface

Library, imported into your own server entry point

Install surface

npm package, also published to JSR

Runtimes

Cloudflare Workers, Deno, Bun, AWS Lambda, Lambda@Edge, Node.js

Dependencies

Web Standard API only, no runtime packages

Router

Pluggable via a constructor option; regexp, trie, linear and pattern implementations ship in the package