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

error-reporting

v0.0.3

Published

Reporting errors to email.

Downloads

2

Readme

error-reporting

Reporting errors to email.

Usage

Usage of this library is fairly simple. All you need to do is to initialize the library and nodemailer's transport and you can start reporting errors immediately.

var error = require('error-reporting');
var nodemailer = require('nodemailer');

// initialize transport
var ses = require('nodemailer-ses-transport');
var transporter = nodemailer.createTransport(ses({
    accessKeyId: 'AWSACCESSKEY',
    secretAccessKey: 'AWS/Secret/key'
}));

// initialize error reporting library
error.init({
    transporter: transporter,
    from: '[email protected]',
    to: '[email protected]',
    subject: 'My Awesome application has encountered an error',
    interval: 60
});

// to report an error, just call error.report() anywhere in your application
var err = new Error();
error.report('A message about your error', {objectThatCasedTheError: {foo: 'bar'}}, err.stack);

Configuration options

  • transporter - Transporter for Nodemailer, see more about SMTP transporter or other transporters. If transporter is not provided, then all errors are printed out to console with stacktrace.
  • from - Any address format accepted by Nodemailer
  • to - Any address format accepted by Nodemailer
  • cc - Array of addresses, format must be accepted by Nodemailer, default is empty array
  • subject - Subject of email, default is 'Error'
  • interval - Interval in seconds for sending messages to email, defaults to 30. If set to 0 or null all errors are sent immediately. Please beware, as this might flood your email server.

Changelog

Changelog is available under GitHub releases section.