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

@unhandled/hono

v0.2.7

Published

Unhandled for Hono on Node.js: route names, users, body capture and error reporting on top of @unhandled/node

Readme

@unhandled/hono

Unhandled for Hono 4.8 or later on Node.js with @hono/node-server. It builds on @unhandled/node, whose HTTP instrumentation creates the server span for every request @hono/node-server receives. This package's middleware names that span after the matched route, adds the user, records request and response bodies when capture is on, reports server errors, and marks the resource with unhandled.framework.name=hono.

Hono on other runtimes (Workers, Deno, Bun) is not covered: the package needs the Node HTTP server span.

Start

UNHANDLED_DSN=https://[email protected]/0b4f6c2e-8a1d-4c3e-9f7a-1234567890ab \
  node --import @unhandled/hono/register server.js

@unhandled/hono/register hooks ES module loading and starts the SDK from UNHANDLED_DSN, UNHANDLED_ENV and OTEL_SERVICE_NAME. Use it rather than @unhandled/node/register, which leaves the framework off the resource.

To pass options in an ES module app, write your own register file and load it with --import:

// instrument.ts
import { startWithEsmHook } from '@unhandled/node/hook'

await startWithEsmHook(async () => {
  const { init } = await import('@unhandled/hono')
  init({ serviceName: 'shop', http: { captureBodies: { enabled: true } } })
})

In CommonJS or a bundled app, call init(options) from @unhandled/hono before anything else is loaded. It takes every @unhandled/node option.

Like @unhandled/node, it redacts secret query values and secret path segments (not ids) from URL attributes by default (http.sanitizeUrls: false turns that off), and reads source lines only from .js/.ts source files under the app root, never from paths named in an error message or from dotfiles such as .env. The @unhandled/node README has the rules.

Middleware

import { serve } from '@hono/node-server'
import { Hono } from 'hono'
import { unhandled } from '@unhandled/hono'

const app = new Hono<{ Variables: { user?: { id: string } } }>()
app.use(unhandled({ user: (c) => c.get('user') }))

app.get('/users/:id', (c) => c.json(loadUser(c.req.param('id'))))

serve({ fetch: app.fetch, port: 3000 })

Register unhandled(options?) first, so every other middleware and handler runs inside it. After the rest of the chain has run, it:

  • sets http.route to the path of the route that answered (from hono/route) and renames the span, for example GET /users/:id. A 404 answered by a use() or all() entry means no route matched, and the span keeps the bare method name.
  • resolves user(c) and writes user.id, user.email and user.name on the server span. It runs after your auth middleware, so c.get(...) values are there.
  • reports c.error with mechanism hono.on_error and the resolved user. Hono sets c.error before it calls your app.onError handler, so a custom handler changes the response but not the report.
  • records the request and response bodies when http.captureBodies is on and the content type is JSON or a URL-encoded form. It never reads a request body itself. It records the body your handler already read with c.req.json() or c.req.text(). For the response it copies a body that is already in memory, and skips a streamed response instead of waiting for it.

Which errors are reported

Every error that is not an HTTPException is reported. An HTTPException is reported only when its status is 500 or higher, because a 4xx HTTPException is a response you chose to send. The client's ignoreExceptions, ignoreStatuses and ignoreCodes rules still apply.