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

@zuiio/capture

v0.1.0

Published

Unified error capture layer — wraps Sentry + console.error with Supabase query error helpers

Readme

@zuiio/capture — Unified Error Capture

Framework-agnostic error capture layer. Apps register a Sentry handler once; everything else just calls capture().

Setup (once per app)

// sentry.client.config.ts or app initialization
import { setCaptureHandler } from "@zuiio/capture";
import * as Sentry from "@sentry/nextjs";

setCaptureHandler((error, ctx) => {
  Sentry.captureException(error, { extra: ctx });
});

When no handler is set, errors still surface via console.error() — safe to use before Sentry initializes.

Exports

| Export | Description | |---|---| | setCaptureHandler(fn \| null) | Register telemetry transport (Sentry, Datadog, etc.). Call once at init. | | capture(error, ctx?) | Report any error to the handler; falls back to console.error. | | captureDbError(cause, queryLabel, error, ctx?) | Capture a Supabase query error with structured tags (db_cause, context). | | captureRedirectLoop(path, count, userId?) | Capture redirect-loop detection as an error. | | CaptureContext | Record<string, unknown> & { context?: string } — extra metadata for every call. | | withDbCapture(label, promise, ctx?) | Wrap a Supabase query — auto-captures on result.error or exception. Returns same { data, error }. | | withSupabaseConsoleCapture() | Returns a fetch wrapper that logs non-OK Supabase responses to console.error. |

Usage

Generic error capture

import { capture } from "@zuiio/capture";

await capture(error, { context: "Dashboard profile query" });

Supabase queries (preferred over manual try/catch)

withDbCapture wraps any Supabase query and automatically reports result.error or thrown exceptions:

import { withDbCapture } from "@zuiio/capture";

const { data, error } = await withDbCapture(
  "getProfile",
  supabase.from("profiles").select("*").single(),
  { orgId },
);

This replaces repetitive if (error) console.error(...) blocks — every query gets consistent error reporting.

Supabase client fetch logging

Drop into createServerClient to log all non-OK Supabase HTTP responses automatically:

import { withSupabaseConsoleCapture } from "@zuiio/capture";

const supabase = createServerClient(url, key, {
  cookies: { ... },
  global: { fetch: withSupabaseConsoleCapture() },
});

Redirect loop detection

import { captureRedirectLoop } from "@zuiio/capture";

if (redirectCount > 5) {
  await captureRedirectLoop(path, redirectCount, userId);
}

Conventions

  • Replace console.error(err) in error paths with capture(err, { context: "..." }).
  • Use withDbCapture for every Supabase query — no manual try/catch.
  • Never call Sentry directly — go through this package so the handler stays swappable.