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

loggert

v0.2.3

Published

Easy and flexible logging

Downloads

9

Readme

Loggert

npm version Build Status Coverage Status Dependency Status devDependency Status

Easy and flexible logging in Node.

Usage

Getting started

For one process, the configuration of Loggert must be set once. Here is an example using some of the built in transports and formatters:

var log = require('loggert')('my-namespace');

var ConsoleTransport = log.transports.Console;
var FileTransport = log.transports.File;

var DefaultFormatter = log.formatters.Default;
var RawFormatter = log.formatters.Raw;

log.setConfig({
    transports: [
        new ConsoleTransport({
            level: 'info', // Log "info" levels and above. 
            // level: ['info', 'error'], // Pass an array to only log "info" and "error" levels. 
            processId: true, // Include the processId in the logs.
            formatter: new DefaultFormatter({
                colorize: true // Tell the formatter to colorize the output.
            })
        })
     ]
});


var x = 200;

// The first argument is always the "message", all following arguments should containg extra info.
log.warn('This is a warning message', { someKey: 'avalue' }, x);

Custom transports and formatters

Transports and formatters are simple objects. Creating a custom transport or formatter is easy. Transports must have a write function and a level property (being one of the log levels or an array of log levels). A formatter must have a format function. Here is an example of a custom transport with a custom formatter:


function MyFormatter (options) {
    this.colorize = options.colorize || false;
}

MyFormatter.prototype.format = function (logObject) {
    var formattedLogObject = logObject.namespace + ': ' + logObject.message;

    if (this.colorize) {
        formattedLogObject = exampleColorFunction(formattedLogObject);
    }

    return formattedLogObject;
};


function CustomTransport (options) {
    if (!options.formatter) {
        throw new Error('CustomTransport transporter has no formatter.');
    }
    this.level = options.level || 'trace' // Default to "trace" level
    this.formatter = options.formatter;
}

CustomTransport.prototype.write = function (logObject) {
    // Write the logObject somewhere.    
    console.log(this.formatter.format(logObject));
}

// Set up loggert;
var log = require('loggert');
log.setConfig({
    transports: [
        new CustomTransport({
            formatter: new MyFormatter({
                colorize: true
            })
        })
    ]
});

Namespaces

Each time loggert is required, a namespace can be defined. The namespace will be added as a prefix to messages. For example:

// webservice.js
var log = require('loggert')('webservice-example');
// database.js
var log = require('loggert')('database-example');

Log levels

There are 6 log levels available. These are functions on the loggert instance. trace is the lowest level, fatal is the highest level.

  1. trace
  2. debug
  3. info
  4. warn
  5. error
  6. fatal