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

yanlog

v1.1.4

Published

Wrapper of winston for easy configuration

Downloads

13

Readme

NPM version Dependencies

yanlog

Wrapper of winston for easy configuration. Inspired by debug and logback

Installation

$ npm install yanlog

Usage

With yanlog you simply invoke the exported function to generate your logger function, passing it a name which will determine the winston wrapper that is returned.

On first invoke, yanlog is going to load the first yanlog.js in app path.

if yanlog's config file is find, every 30s yanlog is watching if the file change and reconfigure yanlog

Example app.js:

var log = require('yanlog')('http')
  , http = require('http')
  , name = 'My App';

// fake app

log.info('booting %s', name);

http.createServer(function(req, res){
  log.info(req.method + ' ' + req.url);
  res.end('hello\n');
}).listen(3000, function(){
  log.error('listening');
});

// fake worker of some kind

require('./worker');

Example worker.js:

var log = require('yanlog')('worker');

setInterval(function(){
  log.debug('doing some work');
}, 1000);

Example yanlog.js:

module.exports = {
    "options": {
        "enableWatch": true
    },
    "configuration": {
        "appender": {
            "name": "console",
            "transports": [{
                "module": "Console",
                "options": {
                    "colorize": true,
                    "timestamp": true
                }
            }]
        },
        "logger": [{
            "name": "http",
            "level": "warn",
            "appender-ref": "console"
        }],
        "root": {
            "level": "info",
            "appender-ref": "console"
        }
    }
}

yanlog.js structure

Options - Optional

  • enableWatch : enable watching file - default: true

Configuration

appender (array or object) - Required

Appender defined all winston logger of your application.

appender object:
  • name: name of appender - Required
  • transports: list of transports (or object) of appender - Required
  • module: name of module. yanlog tests if module exists in winston.transport else it will be imported. list of available transport - Required
  • submodule: submodule (example: "MongoDB" for mongodb-transport) - Optional
  • options: options of module - Optional

logger (array or object)

Logger defined all active loggers

logger object:
  • name: namespace. The * character may be used as a wildcard. Suppose for example your library has debuggers named "connect:bodyParser", "connect:compress", "connect:session", instead of listing all three with different logger, you may simply do connect:* - Required
  • level: level of logger - Optionnal (Default: info)
  • appender-ref: reference to appender - Required

root - Optional

Default logger if no logger matches the current namespace

root object:
  • level : level of logger - Optionnal (Default: info)
  • appender-ref: reference to appender - Required
default root
function getDefaultRootLogger() {
    return logger = new(winston.Logger)({
        transports: [
            new(winston.transports.Console)({
                level: 'info',
                timestamp: true,
                colorize: true
            }),
        ]
    });
}

roadmap

  • add compatibility with yaml and .properties
  • config file testing in order to generate error logs

Change log

here

Authors

License

The MIT License