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

@condux/browser

v0.1.8

Published

Condux SDK for browsers — report errors to Condux, with automatic global error capture.

Readme

@condux/browser

Condux SDK for browsers. Reports errors to a Condux relay in the Sentry "store" wire shape (the relay normalizes it like an official Sentry SDK), and automatically captures uncaught errors and unhandled promise rejections via the global error / unhandledrejection events. Built on the isomorphic @condux/node core, so delivery is the same resilient, never-throwing transport.

Usage

import { init, captureException, Level } from "@condux/browser";

init({
  dsn: "https://<key>@ingest.condux.ai/<projectId>",
  environment: "production",
  release: "[email protected]",
});

// Uncaught errors + unhandled rejections are now reported automatically (as unhandled).
// Capture something manually:
try {
  risky();
} catch (error) {
  captureException(error);
}

Pass captureGlobalErrors: false to init to opt out of the automatic handlers and report only manually.

Every event carries the page it happened on: the URL is read from location.href at capture time and sent as request.url, so an issue says which page produced it without any wiring. Override it, or add tags for one event only, with the third argument:

captureException(error, true, { request: { url: "/checkout" }, tags: { step: "payment" } });

Verify your setup

Silence is what a broken error monitor and a healthy app look like from the outside, so prove the pipeline once. The command ships with @condux/node, so run it without adding a dependency:

CONDUX_DSN="https://<key>@ingest.condux.ai/<projectId>" npx --package=@condux/node condux test-event

Exit code 0 means delivered (the message appears as an info-level issue), 1 means delivery failed and prints why, 2 means the DSN was missing.

Enrichment

setUser / setTag / setContext / addBreadcrumb are re-exported here; whatever you set rides every subsequent event. See the @condux/node README.

Develop

pnpm install --ignore-workspace
pnpm build   # needs ../js (the @condux/node core) built first
pnpm test

Zero runtime dependencies beyond the @condux/node core. The global handlers are unit-tested with a fake event target, so no real DOM is needed.