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/express

v0.2.7

Published

Unhandled for Express: route names, users, body capture and error reporting on top of @unhandled/node

Readme

@unhandled/express

Unhandled for Express 5. It builds on @unhandled/node, which traces the HTTP server, Express middleware, outgoing requests and databases. This package adds the user to each request, records request and response bodies when capture is on, reports server errors from Express's error pipeline, and marks the resource with unhandled.framework.name=express.

Start

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

@unhandled/express/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/express')
  init({ serviceName: 'shop', http: { captureBodies: { enabled: true } } })
})

In CommonJS or a bundled app, call init(options) from @unhandled/express before express is first required. 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 express from 'express'
import { unhandledErrorHandler, unhandledMiddleware } from '@unhandled/express'

const app = express()
app.use(express.json())
app.use(
  unhandledMiddleware({
    user: (req) => (req.user ? { id: req.user.id, email: req.user.email } : undefined),
  })
)

app.get('/users/:id', showUser)

app.use(unhandledErrorHandler())
app.use(yourErrorHandler)

unhandledMiddleware(options?) goes before your routes. user(req, res) runs when the response finishes, so it sees whatever your auth middleware put on the request. The result lands on the request's server span as user.id, user.email and user.name.

unhandledErrorHandler() goes after your routes and before your own error handlers. It reports the error with mechanism express.error_handler, then passes it on with next(err), so your handlers and Express's default response still run. It reports only errors Express answers with a 5xx: an error whose status or statusCode is between 400 and 499 is a client error and is skipped. The report carries the user from unhandledMiddleware, and the client's ignoreExceptions, ignoreStatuses and ignoreCodes rules still apply.

Routes

The Express instrumentation in @unhandled/node names each server span after the matched route (GET /users/:id, mount paths included) and records it as http.route. If you turn that instrumentation off with instrumentations: { '@opentelemetry/instrumentation-express': { enabled: false } }, the middleware fills the route in from req.baseUrl and req.route.path instead. In that mode an error thrown inside a mounted router loses the mount path, because Express resets req.baseUrl once the error leaves the router.

Bodies

With http.captureBodies on, the middleware records the body your body parser produced and the body passed to res.send or res.json. Parsed objects are recorded as JSON. Buffers from express.raw() and streamed responses are not recorded.