Skip to main content

Node.js crash reporting

Your Node service threw at 3 a.m. The log that explains it is on a box you can't reach.

BugSplat captures the uncaught exception or unhandled rejection, attaches the log files you name, and posts the report before the process exits. The chain of causes comes with it, down to the system error underneath.

Why BugSplat for Node.js

Uncaught exceptions and unhandled rejections report with your log files attached and the full chain of causes, before the process exits.

01 · It lands

Something breaks in your Node.js build. You find out first.

Add BugSplat to your uncaught exception and unhandled rejection handlers and every fatal error posts before the process exits. Each report carries the chain of causes, including Node's own code, errno, and syscall properties, and the log files you choose from disk. If the service sits behind a game, matchmaking, telemetry, or builds, it reports into the same dashboard as the game.

  • Uncaught exceptions and unhandled rejections posted before the process exits
  • Log files attached from disk, up to 10MB per report
  • The chain of causes down to the system error, with code, errno, and syscall
A crash report in BugSplat with application, group, exception, platform, and the user's feedback - how Node.js errors arrive

02 · It groups and resolves

A report count is not a bug count.

BugSplat groups Node.js errors your way: your rules decide which call stacks count as the same bug, and the list is ranked by how many people each one hit. Stacks from TypeScript or bundled services resolve against the source maps you upload, so frames point at your source files, not the compiled output.

  • Thousands of reports collapse into a short list of distinct bugs
  • Your own file and line from the source map, not the compiled output
  • OS, hardware, and build on every report
A symbolicated active thread in BugSplat with the faulting frame expanded to its file, line, arguments, and locals

03 · It tells you

Stay ahead of the next one.

Alerting for Node.js errors hits Slack, Discord, or Teams the moment something spikes. Version-over-version analytics show whether each release is more stable than the last.

  • Regressions flagged when a fixed crash comes back
  • Daily and weekly digests with the highlights
A BugSplat new group alert in Discord with the crash group and stack trace

What makes BugSplat different

The backend lands next to the client.

A game's matchmaking or telemetry service reports into the same dashboard as the game, with the same grouping, alerts, and trends. So does any other Node service you run.

Native from the start

BugSplat has been turning minidumps into readable stacks since 2005. Symbols, PDBs, and native crashes are the core of the product.

A bill that holds still

Flat monthly plans with fixed limits. A spike in crash volume after a release doesn't change your bill.

Answered by the people who build it

Email support with a Node.js question and you'll hear back from an engineer who builds BugSplat, usually the same day.

Node.js setup

Wire up Node.js and read a real stack the same day.

Add the SDK and upload source maps with each build. If you get stuck, contact support and you'll reach the engineers who build BugSplat.

By clicking "Accept", you agree to the storing of cookies on your device. View our Privacy Policy .