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

@watchforge/browser

v0.1.1

Published

WatchForge JavaScript SDK for Node.js, Express.js, and React

Readme

WatchForge JavaScript SDK (@watchforge/browser)

Browser and Node SDK for WatchForge. One call to register() turns on automatic error reporting—no manual try/catch required for typical crashes.

What this package does not require

  • No Material UI (MUI) and no other UI library. If npm install fails with errors about @mui/material or @mui/lab, that conflict comes from your app’s existing dependencies, not from WatchForge. Fix or align MUI versions in your project, or install with:

    npm install @watchforge/browser --legacy-peer-deps
  • React is optional. It is only needed if you use the React ErrorBoundary export from @watchforge/browser/react. Plain JavaScript, Vue, Angular, etc. can use the main entry without installing React.

Installation

npm install @watchforge/browser

Quick start (all most apps need)

Call register() once as early as possible (e.g. app entry / main bundle), with your DSN from the WatchForge project settings.

import { register } from '@watchforge/browser';

register({
  dsn: 'https://PUBLIC_KEY@your-host/PROJECT_ID',
  app_env: 'production',  // e.g. development | staging | production
  debug: false,           // true while integrating locally
});

That’s enough for automatic reporting in the browser and Node:

| Where | What gets reported automatically | |--------|----------------------------------| | Browser | Uncaught errors (window.onerror), unhandled promise rejections, plus breadcrumbs (console, clicks, navigation) to give context around failures | | Node | uncaughtException and unhandledRejection |

You do not need to call captureException in normal flows—those global handlers already send errors to WatchForge.

How events reach WatchForge

After register(), the SDK buffers events and sends them to your ingestion endpoint derived from the DSN. Failures are grouped and shown in the WatchForge UI like other SDKs.

Optional: copy files instead of npm

You can copy the src/ folder into your repo and import from your path (same register API).

Advanced (optional APIs)

For manual reporting (handled errors, custom messages, immediate flush), see CONFIGURATION_GUIDE.md in this repository. The main package also exports captureException, captureMessage, and flush if you need them—they are not required for automatic error capture.

Deprecated

init() is deprecated; use register() with a dsn field.

Browser support

Modern browsers with ES modules. For React error boundaries, import from @watchforge/browser/react.