Pagerless for Node.js

Set up

npm i pagerless

import "pagerless/auto"; // first line of your server entry

Set PAGERLESS_KEY (your ingest key from the Pagerless app) in your host's environment. Without it the SDK does nothing, so local dev stays quiet.

CommonJS: require("pagerless/auto"). Or start it in code: require("pagerless").init({ service: "api" }).

What it catches

• Uncaught exceptions and unhandled promise rejections (your process still exits as before; Pagerless flushes for up to 2 seconds first).
• Status and latency for every route of any node:http server, using the route pattern when your framework provides one.
• Failing calls to other services: 5xx, 429 and network errors from fetch, axios, got and the Stripe SDK. Stripe, PayPal, OpenAI, Anthropic, Supabase, Neon, Resend, Twilio and others are tagged by name.
• A heartbeat every 60 seconds, so a silent app wakes you after 5 minutes.
• A deploy marker when the release is known (Vercel, Railway, Render, Heroku, Fly, Cloudflare and GitHub commit variables are read automatically).

Framework hooks

• Next.js

  One line in instrumentation.ts covers pages, layouts, route handlers, server actions and middleware, on Node and the edge.

• Nuxt

  One server plugin hooks Nitro's error hook: API routes, server rendering and middleware.

• SvelteKit

  Export handleError from your hooks

• Astro

  One middleware export, or the integration in astro.config

• Remix and React Router

  Export handleError from the server entry

• Express

  One error handler after your routes

• Fastify

  One call registers an onError hook.

• Koa

  Add it as the first middleware

• NestJS

  One line after NestFactory.create, or register the exception filter yourself.

• Hono

  One middleware right after new Hono(), on every runtime Hono runs on.

• tRPC

  One adapter option

• Bun

  The same one import as Node

• Deno

  One import from npm

• Electron

  Main-process crashes, crashed renderers and GPU or child processes, grouped into problems you can act on.

• React Native and Expo

  JS errors and fatal crashes from your app, sent within 1.5 seconds of a fatal one, with an in-memory queue for when the phone is offline.

Report things yourself

import { capture, event } from "pagerless";

try {
  await chargeCard(order);
} catch (err) {
  capture(err, { route: "POST /checkout", tags: { plan: "pro" } });
  throw err;
}

event({ title: "Refund queue backed up", severity: "tell" });

Settings

Updated October 22, 2026.