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

g4-logger

v0.2.0

Published

A simple winston logger that is configured with some niceties such as listening for a SIGUSR2 change log levels

Downloads

39

Readme

g4-logger

A simple logger that is configured with some niceties such as listening for a SIGUSR2 to change log levels

Log Levels

We use syslog levels RFC-5424 for the level definitions.

  • 0 = Emergency (panic) - Only log panic conditions
  • 1 = Alert (alert) - Only notify on conditions that cause immediate failure from the local system.
  • 2 = Critical (crit) - Notify on conditions that cause immediate failure from the local system or any secondary system or sub system.
  • 3 = Error (error) - Failures that can be recovered from.
  • 4 = Warning (warn) - Indicator that an error will occur if action is not taken.
  • 5 = Notice (notice) - Normal but significant condition. May indicate a potential problem.
  • 6 = Informational (info) - Normal operational messages.
  • 7 = Debug (debug) - Information useful to developers for debugging the application.

Usage

Simply load the module and then call the appropriate message functions.

  var Logger  = require('g4-logger'),
      logger  = Logger({ level: 'debug' });
  
  logger.panic('Everyone panic!');
  logger.log('panic', 'Everyone panic!');
  // should output [panic] - Everyone panic!
  
  logger.crit('A critical error');
  logger.log('crit', 'A critical error.');
  // should output [crit] - A critical error.
   
  logger.error('My terrible error');
  // should output [error] - My terrible error
  
  logger.warn('Beware of codes!');
  // should output [warn] - Beware of codes!
  
  logger.notice('A fancy notice');
  logger.log('notice', 'A fancy notice');
  // should output [notice] - A fancy notice
  
  logger.info('My super message');
  // Should output [info] - My super message
  
  logger.debug('My cool debug message');
  // Should output [debug] - My cool debug message