npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@takibi/hono-adapter

v0.2.3

Published

Typed Hono middleware for Takibi HTTP handlers.

Readme

Takibi Hono adapter

@takibi/hono-adapter mounts a Takibi HTTP handler on Hono.

npm install @takibi/hono-adapter
import { Hono, type Context } from "hono";
import { takibiServer } from "@takibi/hono-adapter";
import { handler } from "./takibi";
import type { AppEnv } from "./env";

const app = new Hono<AppEnv>();
// Install the application's authentication / DI middleware first.
app.route(
  "/api/takibi",
  takibiServer({
    handler,
    createContext: async (c: Context<AppEnv>) => ({
      env: c.env,
      session: await c.var.di.getSession(),
    }),
  }),
);

createContext runs per request and must return the input required by the handler's createTakibi<Input, Env>() declaration. Synchronous and asynchronous suppliers are supported. Empty input is supplied explicitly with () => ({}).

takibiServer returns a Hono app. Mount it with app.route("/api/takibi", server) or app.route("/", server) for the root; no wildcard suffix is needed. The adapter uses Hono's basePath(c) to resolve the complete mount path, including nested mounts and request parameters. Hono owns route matching and parameter resolution.

Takibi receives the original request URL and interprets collection, action and _batch paths. It also handles the prefix root, trailing slashes and invalid deep paths; neighboring prefixes are unaffected. Register more specific application routes before the adapter when they should take priority. An unmatched handler result continues to the next Hono middleware.

Authentication and request-header changes belong to preceding application middleware. The adapter forwards c.req.raw and preserves response headers from outer Hono middleware. WebSocket upgrades (status 101) are returned as the original Response because Hono cannot reconstruct them. The core handler itself has no Hono dependency and can also be called directly with handler.handle(request, { stripPrefix, context }). The adapter passes a stripPrefix function that removes the matched mount path; the original Request is passed through unchanged. Direct callers can supply a literal prefix string instead, or omit it to use the whole pathname.