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

errh

v0.0.5

Published

Simple error messages collector

Downloads

2

Readme

errh - simple error messages collector

Written by Vladimir Neverov [email protected] in 2014.

User provides two parameters: id of something that caused an error to occure and an error message. Id may be absent, so the message can be the only parameter.

ErrorHandler additionally stores level of importance, timestamp, stack trace and arbitrary application and module names that are provided are arguments to the constructor.

Constructor accepts three arguments:

  • task - a general name of the application where errors should be collected
  • id - name of the module
  • settings - error handler settings, reserved for the future

Two first arguments both are arbitrary strings and are used only for error identification by humans.

These errors can later be handled in an arbitrary way, e.g. printed to console, stored in a database, emailed, etc.

Error register interface:

  • .info(message)
  • .info(id, message) - register a message at 'info' level
  • .warn(message)
  • .warn(id, message) - register a message at 'warning' level
  • .fatal(message)
  • .fatal(id, message) - register a message at 'fatal' level

All the methods above does not return anything by convention, so you can do as follows to return undefined:

return errh.fatal(id, "Cant' bear it anymore")

Other methods:

  • .list() - return errors as array
  • .merge(list) - merge with array of errors or another ErrorHandler instance, returns current ErrorHandler instance
  • .stat() - return object with minimal statistics on errors

.toString method is redefined so that it returns a string representation of errors, one error per line, so you can feed ErrorHandler instance to console.log, for example. .inspect returns .toString().

TODO: add adapters for printing, storing, emailing, etc.