website

Adds StitchAPI to the Utilities section of the third-party middleware list. is Hono middleware for StitchAPI: it puts a per-request on the context () — a principal-bound handle for typed, validated, resilient outbound API calls — plus an SSE streaming helper () and a Stitch-error → HTTP mapper. Every import is from or (no ), so it runs on Node, Cloudflare Workers, Deno, Bun and Vercel Edge. Placed alphabetically within Utilities (between Session and tsyringe).

Hi Hono team and contributors! 👋 I am the author of InferDI. I noticed that InferDI is already mentioned in your documentation (https://hono.dev/docs/middleware/third-party), which I truly appreciate! Given the growing interest in architecture patterns for scalable TypeScript applications, I would like to propose creating a dedicated "Dependency Injection" page under the Guides section on the Hono website. Why InferDI is a perfect fit for Hono I designed InferDI with the same philosophy as Hono: speed, simplicity, and zero bloat. Here is why a dedicated guide featuring it would bring great value to Hono users: Type-Safe DI Graph (Compile-Time Validation):* Unlike traditional containers that fail at runtime or production, InferDI’s DI graph is a type. This catches circular dependencies, missing providers, and type mismatches instantly during development via TypeScript compilation. Blazing Fast Performance: Benchmarks show near-native resolution speeds, significantly outperforming legacy DI libraries by minimizing runtime reflection overhead. Perfect for Serverless & Edge: Zero-reflection architecture means near-zero startup time and minimal memory footprint, making it ideal for AWS Lambda, Cloudflare Workers, and Vercel functions. Zero Configuration, Any Runtime: Works straight out of the box in Node.js, Deno, Bun, and browsers without tedious build steps, experimental decorators, or setup. Modern Architecture & Robust Inference: Full TypeScript support with powerful type inference, making container configuration predictable, clean, and completely error-free. Zero Dependencies: Keeps your production bundle clean, lean, and secure. Global Accessibility: Full, high-quality documentation is completely localized and available in English, Chinese, Japanese, Spanish, and Russian at inferdi.com. Native Integration:* We already have an official, production-ready adapter specifically for Hono: @inferdi/hono. Proposed Content A standalone "Dependency Injection" guide would help developers structure larger Hono projects. I propose including: A quick introduction to DI in edge/serverless environments. A clean, step-by-step example using to show how easily it integrates out of the box. Best practices for managing dependencies inside Hono middleware and route handlers. Since I am the creator of InferDI, I would be more than happy to draft this guide, write the code examples, and submit a Pull Request myself if you approve this idea. Let me know what you think! Thank you for building such an incredible framework. 🚀

What Adds a new example — InferDI (Dependency Injection) — under Examples → 3rd-party Middleware*, with a matching sidebar link. The guide walks through using InferDI's official request-scope middleware in a Hono app: building a typed DI container with / / lifetimes wiring and typing the context via hydrating the per-request scope with resolving services in handlers through the middleware options table and streaming () Why Implements the proposal agreed in #869. Notes All code samples are checked against the published API. Formatted with the repo's Prettier config. Closes #869