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

@pumped-fn/lite-hono

v0.2.4

Published

Hono middleware helpers for @pumped-fn/lite request execution contexts

Downloads

659

Readme

@pumped-fn/lite-hono

Hono middleware for carrying a request-local @pumped-fn/lite execution context through Hono's typed Variables.

import { createScope, flow, tag, tags } from "@pumped-fn/lite"
import { Hono } from "hono"
import { hono } from "@pumped-fn/lite-hono"

const requestId = tag<string>({ label: "request.id" })
const readRequest = flow({
  deps: { requestId: tags.required(requestId) },
  factory: (_ctx, deps) => deps.requestId,
})

type AppEnv = hono.Env

const lite = hono.adapter()
const scope = createScope({ extensions: [lite] })
const app = new Hono<AppEnv>()

app.use(
  "*",
  lite.middleware({
    tags: (request) => [requestId(request.headers.get("x-request-id") ?? "missing")],
  })
)

app.get("/request-id", async (context) => {
  return context.json({
    requestId: await context.var.lite.exec({ flow: readRequest }),
  })
})

API

hono.adapter(options) creates a Lite extension with Hono middleware methods. Install the adapter object in createScope({ extensions }), then mount lite.middleware(options) in Hono.

The middleware creates a fresh execution context per request and stores it in context.var.lite. Route handlers run flows from that framework-owned request surface.

Use tags.required(...) for framework-provided request tags that a flow needs. This keeps tag requirements visible to dependency analysis instead of hiding them in ad hoc context reads. Flows and resources that consume request-derived values should declare those values in deps; route handlers seed tags at the framework boundary and then execute public Lite units.

Pass key to use another Hono variable name. Pass close: false if an outer framework boundary owns ctx.close(...).


Part of pumped-fn — start with the docs or the mental model.