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

v0.2.7

Published

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

Readme

@unhandled/nestjs

Unhandled for NestJS 11 on the Express platform. It builds on @unhandled/node, which traces the HTTP server, Express, Nest's controllers, outgoing requests and databases. This package's module adds the user to each request, records request and response bodies when capture is on, reports server errors from Nest's exception layer, and marks the resource with unhandled.framework.name=nestjs.

The Fastify platform is not supported yet.

Start

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

@unhandled/nestjs/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. It works for CommonJS builds too, which is what the Nest CLI emits by default.

To pass options, either write your own register file for --import:

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

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

or, in a CommonJS build, call init(options) from @unhandled/nestjs on the first line of main.ts, before @nestjs/core is imported. 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.

Module

import { Module } from '@nestjs/common'
import { UnhandledModule } from '@unhandled/nestjs'

@Module({
  imports: [
    UnhandledModule.forRoot({
      user: (host) => {
        const { user } = host.switchToHttp().getRequest()
        return user ? { id: user.id, email: user.email } : undefined
      },
    }),
  ],
  controllers: [UsersController],
})
export class AppModule {}

UnhandledModule.forRoot(options?) registers two global providers.

  • UnhandledInterceptor (APP_INTERCEPTOR) runs after your guards. It sets http.route from the Express route that matched, global prefix included, and renames the span, for example GET /users/:id. It resolves user(host) and writes user.id, user.email and user.name on the server span. With http.captureBodies on, it records the parsed request body and the value your handler returned. Returned objects are recorded as JSON. Strings, buffers and streams are not recorded, because Nest picks their content type only while it writes them.
  • UnhandledExceptionFilter (APP_FILTER) extends BaseExceptionFilter. It reports the error with mechanism nestjs.exception_filter and the resolved user, then lets the base filter send Nest's usual response.

Which errors are reported

Any error that is not an HttpException is reported, and so is an HttpException with a status of 500 or higher. NotFoundException, BadRequestException, validation pipe errors and every other 4xx HttpException are responses you chose to send, so they are skipped. The client's ignoreExceptions, ignoreStatuses and ignoreCodes rules still apply.

Nest hands an error to the first global filter that catches it. If your app registers its own catch-all filter, that filter wins and nothing is reported. Extend UnhandledExceptionFilter instead of BaseExceptionFilter in that filter and call super.catch(exception, host), or call reportException from @unhandled/node/framework yourself.

The filter covers HTTP requests. Microservice and WebSocket handlers are not reported.

Instrumentation

The Express and NestJS instrumentations in @unhandled/node stay on and add middleware and controller spans. The module creates no spans of its own. If you turn the Express instrumentation off to drop the middleware spans, the interceptor still names the route.