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

@sprint-logger/web

v0.1.1

Published

Sprint Signals error logger for browser apps (Next.js, Vite, CRA, Astro). Import { init, capture } and call init(key) once — no script tag. Pseudonymous, PII-safe.

Readme

@sprint-logger/web

Sprint Signals error logger for bundled browser apps (Next.js, Vite, CRA, Astro). Import and init() once — no <script> tag.

npm i @sprint-logger/web
import { init, capture, captureMessage } from "@sprint-logger/web";

// once, at app start (e.g. Next.js instrumentation-client.ts)
init("sk_sig_xxx", { release: "1.2.3" });

// uncaught errors + unhandled rejections are captured automatically.
// for handled errors:
try { await save(); }
catch (e) { capture(e, { route: "/editor", severity: "high" }); }

API

  • init(key, { release?, origin?, installGlobalHandlers?, onError?, detectDeadClicks?, captureHttpErrors?, capturePerf?, captureConsoleErrors? }) — call once. A missing/invalid key is a silent no-op. SSR-safe. The four capture*/detect* flags are v2 auto-detectors, all default true.
  • capture(error, { route?, severity?, userToken?, breadcrumbs? }) — manual capture (handled: true).
  • captureMessage(message, ctx?) — capture a string.

Capture more than errors (v2)

Signals now catches bugs that never throw — dead/rage clicks, silent HTTP failures, slow ops — through the same pipeline (group → inbox → triage → task → QA closes it). v1 above is unchanged; v2 is additive.

Auto-detectors — on by default via init flags, set false to disable:

  • detectDeadClicks — absence-of-effect detector (dead + rage clicks).
  • captureHttpErrors — emits an http_error signal on a handled 4xx/5xx (+404).
  • capturePerf — emits a perf signal when long-task/LCP/INP/CLS exceeds its Core-Web-Vitals "good" threshold.
  • captureConsoleErrors — auto-captures every console.error as a low-severity error signal (retroactively covers caught-and-logged errors, zero edits). May surface existing logs on first upgrade → set false or mute the group if noisy.

Assert an app-level problem the SDK can't infer:

import { captureSignal, startSpan } from "@sprint-logger/web";

// business-invariant violation
captureSignal({ type: "cart.empty-after-add", title: "Cart empty after add", severity: "high" });

// time an op — emits `slow_operation` ONLY if it exceeds thresholdMs (default 1000)
const span = startSpan("checkout.submit", 1500);
await submit();
span.finish({ items: cart.length });
  • captureSignal({ type, title, severity?, fingerprint?, context?, route?, userToken? })type is the stable low-cardinality fingerprint seed.
  • startSpan(op, thresholdMs?){ finish(extra?) }.

React 19 boundary bridge — boundary-caught render errors never reach window.onerror, so wire once:

import { signalsReactErrorHandler } from "@sprint-logger/web";
createRoot(el, { onCaughtError: signalsReactErrorHandler(), onUncaughtError: signalsReactErrorHandler() });

Privacy

Pseudonymous only. Sends message, normalized stack, an opaque per-browser userToken (never an email/name/IP), route/release, and non-identifying env (platform, OS, browser, device, timezone, locale, viewport, network, handled, error type). The server rejects PII.

The sk_sig_… key is a project selector, not a secret — mint it in your Sprint project's Signals settings.

MIT