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

@exodus/error-tracking

v3.3.0

Published

A simple error tracking package to let any feature collect errors and create the report

Readme

@exodus/error-tracking

A simple namespaces error tracking package to let any feature collect errors and create the report

Install

yarn add @exodus/error-tracking

Usage

This feature is designed to be used together with @exodus/headless. See using the sdk.

Play with it

  1. Open the playground https://exodus-hydra.pages.dev/features/errors
  2. Try out the some methods via the UI. These corresponds 1:1 with the exodus.errors API.
  3. Run in the Dev Tools Console:
await exodus.errors.track({
  namespace: safeString`balances`,
  error: new Error('Encountered an issue when computing total balances'),
  context: {},
})

API Side

See using the sdk for more details on how features plug into the SDK and the API interface in the type declaration.

import { safeString } from '@exodus/safe-string'
import type { SafeContextType } from '@exodus/errors'

// Track error with optional context (see SafeContextType for available properties).
const context: SafeContextType = {
  /* ... */
}
await exodus.errors.track({ namespace: safeString`wallet`, error, context })

Important: The namespace parameter must be a SafeString to prevent dynamic values from being used. Use the safeString template tag from @exodus/safe-string:

// ✅ Correct - safe string namespace
await exodus.errors.track({
  namespace: safeString`balances`,
  error: new Error('Failed to compute balances'),
})

// ❌ Incorrect - plain strings not allowed
const NAMESPACE = 'my-namespace'
await exodus.errors.track({
  namespace: NAMESPACE,
  error: new Error('Some error'),
})

If you're building a feature and like to use error tracking inside that feature, you can depend on errorTracking and will receive the module with a track method that is auto-namespaced to your feature id.