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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@jacobmarshall/bugsnag-js

v0.0.2

Published

A bunch of small re-implementations of the Bugsnag JS notifier for modern web apps

Downloads

2

Readme

@jacobmarshall/bugsnag-js

A bunch of small re-implementations of the Bugsnag JS notifier for modern web apps.

Please be warned, this module is currently unstable and untested. Please do not use in production unless you know the limitations.

This module is also useful for embedding into smaller libraries, frameworks, or SDKs which wish to report their own errors. It does not automatically notify when there are errors uncaught on the page, you are expected to bring that functionality along with you.

Example

import { config, notify } from '@jacobmarshall/bugsnag-js';

config.apiKey = 'f48d2ed7b8e059aaf02dfda1528a1b8e'; // Add your own api key here
config.releaseStage = process.env.NODE_ENV;
config.user = {
  // Put your user's sharable information here
};
config.endpoint = 'https://bugsnag.local:49000/js'; // If you're lucky enough to run Bugsnag enterprise

try {
  throw new Error('Uh oh...');
} catch(err) {
  notify(err, {
    severity: 'info',
    metaData: {
      // Additional error metadata
    }
  });
}

Configuration

These are some of the currently supported configuration options. Excuse the lack of documentation, it will be coming.

apiKey string

The notifier API key for the project you want the errors to be sent to.

endpoint string

The on-premise/enterprise js notifier URL. Looks something like https://bugsnag.local:49000/js when you're testing.

releaseStage string

The current release stage - these are some common release stages; beta, production, staging, testing, development.

metaData Object<string, *>

The global/default metaData attached to every error sent via the notify function. The notify function can override these defaults if the same key is used (top level, not deep).

appVersion string

The version number of your application. Used to help track when errors were introduced.

severity string

The default severity for all errors (unless overridden). This is set to error by default. Can be one of these three; info, warning, error.

License

MIT License