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.2.6

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.

Readme

@luckystack/error-tracking

Optional error-tracking integration for LuckyStack. Auto-wires error/performance capture into the framework's hook surface and request transports. Currently Sentry-backed; the package name is implementation-agnostic so future adapters (Datadog, etc.) can slot in without renaming consumers' imports. 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 (called by @luckystack/login on login/logout). | | 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:

  • apiError, syncError — capture exceptions thrown from _api/*.ts and _sync/*.ts handlers (already tryCatch-wrapped at the call site).
  • preApiExecute / postApiExecute and preSyncFanout / postSyncFanout — performance spans + breadcrumbs with redacted input/output.
  • postLogin / postLogout — call setSentryUser to attach session identity to subsequent events.

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):
    • @sentry/node@^10.48.0

License

MIT — see LICENSE.