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

bugnet

v0.1.1

Published

Capture bugs.

Downloads

160

Readme

bugnet

Capture Javascript errors. Minimal version of rollbar, bugsnag, etc.

build status coverage license version downloads

Usage

Simply pass the function you wish to use for being notified of errors. As soon as you include bugnet in your application errors will start to be captured and buffered until they're ready to be consumed later. It is recommended you include bugnet as soon as possible in your application.

Importantly bugnet will NOT squelch your application errors (i.e. not a silent catch-all) - it simply monitors them.

npm install --save bugnet
import capture from 'bugnet';

capture((error) => {
	// ...
});

Examples

Browser

Send browser errors to an off-site logger:

import capture from 'bugnet';

// Add event handler.
capture((error) => {
	const request = new XMLHttpRequest();
	request.open('http://errors.myapp.com/', 'POST', true);
	request.send(JSON.stringify(event));
});

Node

Send node.js errors to the console:

// example.js
import capture from 'bugnet';

// Add event handler.
capture((error) => {
	console.log('Got error', error);
});

To start capturing errors at the earliest possible point, load bugnet from node itself.

#!/bin/sh
node -r bugnet ./example.js

TODO:

  • Testing
  • Fix incompatibilities using Object.* methods