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

@dispatchitapp/node

v1.0.0

Published

Node.js server SDK for Dispatch: global error handlers, V8 stack frames with source context, on top of @dispatchitapp/core.

Readme

@dispatchitapp/node

The Node.js server SDK for Dispatch. Builds on @dispatchitapp/core, adding the two things a server needs that the core can't do portably:

  • V8 stack frames with source context — in-app frames carry the lines around the failing line (pre_context/context_line/post_context), read from disk, exactly like the gem.
  • Global error handlersprocess uncaughtException / unhandledRejection, the runtime-level analogue of the gem's Rack middleware + Rails.error subscriber.
import { init, captureException, report } from "@dispatchitapp/node";

init({
  apiKey: process.env.DISPATCH_API_KEY!,
  environment: process.env.NODE_ENV,
  release: process.env.GIT_SHA,
  // installGlobalHandlers: true (default) — capture uncaught errors + rejections
});

try {
  doRiskyThing();
} catch (err) {
  captureException(err, { tags: { area: "import" } });
}

Framework middleware (Express, Fastify) lands in @dispatchitapp/express / @dispatchitapp/fastify and builds on this package. Everything from @dispatchitapp/core is re-exported here, so a Node app imports solely from @dispatchitapp/node.

Notes

  • init sets platform: "node", the dispatch-node SDK identity, and a source-context stack parser rooted at cwd (default process.cwd()). in_app = under the project root and not in node_modules / node: internals.
  • The handlers preserve Node's native crash behavior — capture, then print the error and exit(1) (registering a listener would otherwise suppress both). uncaughtException: override with onFatalError or exitOnUncaught: false. unhandledRejection: fatal by default exactly like Node's own --unhandled-rejections=throw; opt out with exitOnUnhandledRejection: false (this keeps the process alive, which Node alone would not).
  • Shutdown flush: the event queue drains on beforeExit and before any fatal exit, budgeted by shutdownTimeout (ms, default 3000; the gem's shutdown_timeout analogue). Disable the beforeExit hook with flushOnBeforeExit: false. Fatal events are tagged source: uncaughtException / unhandledRejection (the gem's at_exit / rake analogues).

Scripts

pnpm test · pnpm typecheck · pnpm build