mcpField
E
error-tracking-hono

error-tracking-hono

github.com/posthogDevelopment76104 installsUpdated today
Repository

About error-tracking-hono

A skill for developers adding PostHog error tracking to Hono applications. It covers exception capture, source maps, alerts, and issue management while preserving existing error handling.

Key features

  1. 01Configure exception autocapture
  2. 02Capture exceptions at error boundaries
  3. 03Upload source maps
  4. 04Configure error alerts
  5. 05Search and assign issues

Use cases

  1. 01Add error tracking to an existing Hono app
  2. 02Map stack traces to original source
  3. 03Alert on errors and assign issues to teammates

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/posthog/skills --skill error-tracking-hono

After installing, type/error-tracking-honoin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
alerts.md
assigning-issues.md
fingerprints.md
hono.md
monitoring.md
upload-source-maps.md

Details

From the project README

PostHog error tracking for Hono

This skill helps you add PostHog error tracking to Hono applications.

Reference files

  • references/hono.md - Hono error tracking installation - docs
  • references/fingerprints.md - Fingerprints - docs
  • references/alerts.md - Send error tracking alerts - docs
  • references/monitoring.md - Monitor and search issues - docs
  • references/assigning-issues.md - Assign issues to teammates - docs
  • references/upload-source-maps.md - Upload source maps - docs

Consult the documentation for API details and framework-specific patterns.

Key principles

  • Environment variables: Always use environment variables for PostHog keys and host URLs. Never hardcode them.
  • Minimal changes: Add error tracking alongside existing error handling. Don't replace or restructure existing error handling code.
  • Autocapture first: Enable exception autocapture in the SDK initialization before adding manual captures.
  • Source maps: Upload source maps so stack traces resolve to original source code, not minified bundles.
  • Manual capture for boundaries: Use captureException() at error boundaries and catch blocks for errors that don't propagate to the global handler.

Framework guidelines

No specific framework guidelines.

Comments

Markdown supported