12 docs tagged with "HttpRouter"

Analog.js API routes are powered by h3. Use fromWebHandler from h3 to convert winter-tc request handler into h3 request handler.

HttpRouter is adapter-based: it delegates URL pattern matching to a Hono Router instance. Any existing Hono-compatible adapter can be used interchangeably with the HttpRouter class.

HttpRouter relies on the Hono router adapter interface for URL pattern matching and request dispatching. It does not ship with a built-in router. Instead, you supply a Hono Router instance that satisfies the adapter interface.

HttpRouter implements the WinterTC fetch standard, exposing a fetch(request Response | Promise method. This makes it compatible with any framework, runtime, or platform adapter that accepts a standard fetch handler.

The eridu-tech/http-router component provides a framework-agnostic HTTP router built on top of the Hono router engine. It implements the Winter TC fetch object standard, which means it exposes a standard fetch(request): Response signature. This allows it to be integrated directly into any runtime or framework that supports the Fetch API including Node.js, Bun, Deno, Cloudflare Workers, Next.js, Nuxt, SvelteKit, and more.

HttpRouter can be used directly with Next.js App Router route handlers.

HttpRouter can be used directly with Next.js Pages Router route handlers.

Use the @hono/node-server adapter to serve HttpRouter on Node.js.

Nuxt API routes are powered by h3. Use fromWebHandler from h3 to convert winter-tc request handler into h3 request handler.

SolidStart supports fetch-based route handlers natively.

HttpRouter works with SvelteKit server endpoints via the standard Request/Response API.

TanStack Start uses Vinxi under the hood and supports standard fetch handlers.