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

node-alert

v0.1.1

Published

A Node.js library to send alerts through various channels (mail, IRC, push services)

Downloads

8

Readme

node-alert

node-alert is a module whose primary purpose is to provide ways to alert you in the event of an error/crash

Features

  • Extensible : All alert systems are built as plugins and are available under lib/services
  • Lazy requires : The packages required by the plugins will only be downloaded if the user has asked for the plugin and if the package is not already available
  • Straightforward APIs : node-alert doesn't have any APIs of its own. APIs exposed by plugins will be available to the user
  • Easy to author plugins : Plugin architecture is based on Broadway, which makes it easy to write plugins. Check out mail plugin for an example.

Example usage for mail plugin

var alert = require('node-alert')({
  plugins : {
    mail : {
      nodemailer : {
        port : 25,
        host : "smtp.myserver.com",
        auth : {
          user : "[email protected]",
          pass : "mypass"
      },
      message   : {
        addressed_to : "node-alert maintainer",
        serviceName : "Node-Alert test"
      }
    } 
  }
});

alert.alertMail(new Error('Test Error'), function(err, info) {
  if (err) console.log(err);
  else console.log('Success!');
});

Usage guidelines

  • node-alert based services should not be used to handle process.on('uncaughtException'). Use Domains instead.

Plugin Authoring Guidelines

  • Plugins are based on Broadway and have to adhere to their conventions
  • One service per plugin
  • Avoid cross-dependency with other plugins
  • Only expose those API that are useful
  • Lazy load modules. If using any service, use the require-helper. For example, see the mail plugin.
  • Provide README.md with every plugin, containing at least one example of usage. (Example: mail plugin's README)
  • Folder name of the plugin will be the same as the option the user will be expected to provide (Example: mail plugin requires that the user provide options to the plugin under mail. Check the example provided above)