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

@luckystack/error-tracking

v0.8.3

Published

Optional error-tracking integration for LuckyStack (currently Sentry-backed). Auto-wires error/performance capture into the framework's hook surface and request transports. No-op when DSN is missing.

Downloads

3,881

Readme

@luckystack/error-tracking

Optional error-tracking integration for LuckyStack. Auto-wires error/performance capture into the framework's hook surface and request transports. Ships a backend-agnostic ErrorTracker adapter contract plus three built-in adapters — Sentry (@sentry/node), Datadog (dd-trace + hot-shots), and PostHog (posthog-node) — that can be registered together with fan-out. The package name is implementation-agnostic so further backends (CloudWatch, New Relic, ...) can slot in without renaming consumers' imports. The legacy single-Sentry entry is a no-op when SENTRY_DSN is missing.

Install

npm install @luckystack/error-tracking @sentry/node

@sentry/node is a peer dependency.

Quickstart

Call initializeSentry() once at boot — before createLuckyStackServer.

import { initializeSentry } from '@luckystack/error-tracking';
import { createLuckyStackServer } from '@luckystack/server';

initializeSentry();

const server = await createLuckyStackServer({ /* ... */ });
await server.listen();

Set SENTRY_DSN in your environment to enable. Without it, every export is a safe no-op so you can keep the import in production code unconditionally.

Public API

| Export | Purpose | | --- | --- | | initializeSentry() | Read SENTRY_DSN, sample rates, and init the SDK. Idempotent. | | captureException(error, context?) | Forward to Sentry; called by tryCatch automatically. | | captureMessage(msg, level?, context?) | Manual breadcrumb-style logging. | | setSentryUser(user \| null) | Attach session identity. Not called by @luckystack/login directly — identity is propagated by this package's auto-instrumentation hooks (preApiValidate / preSyncAuthorize set it; postLogout clears it). | | startSpan(name, op) | Performance tracing wrapper — used by API/sync request handlers. | | registerSentryConfig(input) / getSentryConfig() | Per-package config registry. Owned by this package; not part of @luckystack/core's ProjectConfig. |

What gets auto-instrumented

initializeSentry() registers handlers on the framework's hook surface:

  • preApiValidate / preSyncAuthorize — attach session identity (setSentryUser / setCurrentErrorTrackerIdentity) as early as each pipeline carries user.
  • preApiExecute / postApiExecute and preSyncFanout / postSyncFanout — performance spans + breadcrumbs with redacted input/output.
  • postLogout — clear the identity so a subsequent anonymous request is not attributed to the logged-out user.

Handler exceptions are NOT captured via an apiError/syncError hook subscription — they flow through tryCatch -> captureException (see below).

tryCatch (from @luckystack/core server entry) calls captureException automatically, so consumer-code errors flow into Sentry without explicit wiring.

Sample rates and ignore-list come from this package's own registerSentryConfig({...}). Breadcrumb redaction keys come from registerRedactedLogKeys(...) in @luckystack/core.

Related architecture docs

  • Error-tracking covers the "why did it break?" half (stack traces, breadcrumbs, error grouping). The "what happened?" half (input/output audit trail, metrics, RUM) is planned for a future @luckystack/monitoring package that lives in its own repo — see docs/ROADMAP.md.

Dependencies

  • Runtime: @luckystack/core
  • Peer (canonical ranges, standardized 2026-05-07; all optional — install only what the adapters you use need):
    • @sentry/node@^10.66.0 — required only when createSentryAdapter() or initializeSentry() is called.
    • dd-trace@^5.0.0 — required only when createDatadogAdapter(...) is called. Import dd-trace as the FIRST require in your server entry.
    • hot-shots@^10.0.0 — optional StatsD companion for the Datadog adapter (metrics). The adapter still captures exceptions without it.
    • posthog-node@^4.0.0 — required only when createPostHogAdapter(...) is called.

License

MIT — see LICENSE.