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

@upgoose/node

v0.1.0

Published

Upgoose error tracking for Node.js servers

Readme

@upgoose/node

Error tracking for Node.js servers, from Upgoose.

Zero dependencies. Node 18+.

Install

npm install @upgoose/node

Use

Call init() once, as early as possible:

import * as Upgoose from "@upgoose/node";

Upgoose.init({
  dsn: process.env.UPGOOSE_DSN,
  environment: process.env.NODE_ENV ?? "production",
  release: process.env.BUILD_SHA,
});

With Express, register the error handler after all routes. It reports the error with its request context and passes it on, so your own error handling is unchanged:

app.use(Upgoose.errorHandler());

Report by hand anywhere:

try {
  await chargeCard(order);
} catch (err) {
  Upgoose.captureException(err, { orderId: order.id });
  throw err;
}

Crashes

Uncaught exceptions and unhandled rejections are reported by default. The report is sent before the process exits (waiting at most 2 seconds), and then the process exits exactly as Node would have: the error is printed and the exit code is 1. A crash is never swallowed. If your app installs its own uncaughtException or unhandledRejection handler, that handler decides what happens next.

Turn this off with captureUncaught: false.

Shutdown and serverless

Reports are sent in the background. Before a graceful shutdown, or at the end of a serverless handler, wait for them:

await Upgoose.flush(); // resolves false if it hit the 2s timeout

What is sent

The error message and stack, your environment and release, and for errors caught by errorHandler() the request method, path, user agent and x-request-id. Headers are never sent wholesale, so cookies and bearer tokens stay on your server, and the query string is dropped from the path. Use beforeSend to redact or drop anything else:

Upgoose.init({
  dsn: process.env.UPGOOSE_DSN,
  beforeSend: (event) => (event.message.includes("ECONNRESET") ? null : event),
});

The DSN key

The key in the DSN is write-only and publishable: it is the same kind of key a browser bundle ships. Give server-side services their own Upgoose project rather than reusing the browser project's DSN, so browser and server errors don't share one key and one release timeline.

License

BSD-3-Clause