error-tracking-node

Configure PostHog exception tracking for Node.js applications with source maps.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/FrekiManagarm/dunlo --skill error-tracking-node-frekimanagarm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-tracking-node
Source: https://github.com/FrekiManagarm/dunlo/tree/main/.agents/skills/error-tracking-node
Command: npx skills add https://github.com/FrekiManagarm/dunlo --skill error-tracking-node-frekimanagarm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you add reliable PostHog error tracking to Node.js apps so exceptions are automatically captured, grouped into actionable issues, and easier to monitor and debug.

Core Features & Use Cases

  • Node.js server-side error tracking setup: Install and initialize the correct PostHog SDK for server environments, including exception autocapture.
  • Better exception capture boundaries: Manually capture exceptions at defined error handling points (for example, route handlers and global error middleware).
  • Improved issue grouping with source maps: Upload source maps so stack traces resolve to original source code, producing more accurate fingerprints and grouping.
  • Monitoring and workflow support: Use PostHog’s issue monitoring, search, fingerprints, and alerting concepts to triage production errors faster.

Quick Start

Add PostHog error tracking to your Node.js app by initializing posthog-node with enableExceptionAutocapture enabled, uploading source maps during your build, and capturing exceptions in your application’s error handler or boundaries.

Frequently Asked Questions about error-tracking-node

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up PostHog error tracking in a Node.js application?

PostHog error tracking in Node.js requires initializing the posthog-node SDK with enableExceptionAutocapture enabled, uploading source maps during your build, and calling captureException in your error handling boundaries to automatically surface and group runtime failures.

Why do I need source maps for PostHog exception monitoring in Node.js?

Source maps are needed for PostHog exception monitoring to resolve minified stack traces back to original source code, producing more accurate fingerprints and better issue grouping for your Node.js production errors.

Can I use posthog-js for server-side Node.js error tracking?

No, server-side Node.js error tracking requires the posthog-node SDK, not posthog-js. You must initialize posthog-node with enableExceptionAutocapture to automatically capture uncaught and unhandled exceptions in your server environment.

How do I manually capture exceptions in Node.js route handlers with PostHog?

To manually capture exceptions in Node.js route handlers, use the captureException method at defined error handling points such as global error middleware or specific route handlers, ensuring runtime failures are grouped into actionable issues.

What is the best way to monitor Node.js runtime failures in production?

The best way to monitor Node.js runtime failures is using PostHog issue monitoring with exception autocapture enabled, combined with manual captureException calls in error boundaries and source map uploads for accurate stack traces and alerting.