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

@zearaez/sniff-js

v1.0.3

Published

Frontend error tracking and logging library

Readme

@zearaez/sniff-js

A lightweight JavaScript error tracking and logging library for frontend applications.

npm version

Features

  • Automatic error capture for JavaScript exceptions
  • Promise rejection tracking
  • Network request error monitoring (fetch and XHR)
  • Console error logging
  • Manual log submission
  • Environment detection (dev/prod)
  • Development mode control

Installation

npm install @zearaez/sniff-js

Quick Start

import { Sniff } from '@zearaez/sniff-js';

// Initialize with your project
const sniff = new Sniff({
  endpoint: 'your-reporting-api-endpoint'
});

// Now errors will be automatically captured and reported

Configuration

The Sniff class accepts the following options:

interface SniffOptions {
  endpoint?: string;     // Custom reporting endpoint of your app
  enableInDev?: boolean; // Enable logging in development mode (false by default)
}

You must provide endpoint parameter.

Usage

Manual Logging

// Log a message with optional metadata
sniff.log('User clicked checkout button', {
  userId: 123,
  cartValue: 59.99
});

Environment Detection

By default, logs are only sent in production environments. @zearaez/sniff-js automatically detects production environments by checking:

process.env.NODE_ENV === "production" || import.meta.env?.MODE === "production"

To enable logging in development environments, set the enableInDev option to true.

How It Works

@zearaez/sniff-js works by:

  1. Setting up global error handlers via setupGlobalHandlers to catch JavaScript errors
  2. Intercepting network requests with setupNetworkInterceptors to monitor fetch and XHR failures
  3. Sending error data to your specified endpoint using the Navigator.sendBeacon API

API Reference

Sniff Class

  • constructor(options: SniffOptions): Initialize the error tracking
  • log(message: string, meta?: Record<string, any>): Send manual logs with optional metadata

Building from Source

npm run build

This will generate compiled output in the dist directory.

Browser Compatibility

@zearaez/sniff-js works in all modern browsers that support:

  • Navigator.sendBeacon
  • Promise
  • fetch API

License

MIT