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

bem-site-logger

v0.0.5

Published

Simple logger module for bem-site projects. It is simple wrapper around node console methods.

Downloads

28

Readme

Logger

Simple logger module for bem-site projects. It is simple wrapper around node console methods.

NPM

Coveralls branch Travis David David

GitHub Logo

Usage

Add logger dependency to your project:

npm install --save bem-site-logger

Add logger requirement to the code of your module:

var logger = require('bem-site-logger').createLogger(module);
logger.info('Hello World');

Advanced configuration

Your can override some default logger options by:

var options = {
        level: 'debug',
        color: false,
        useDate: false
    },
    logger = require('bem-site-logger').setOptions(options).createLogger(module);

Where available options are:

  • level - logger verbosity level. Can be one of 5 available values: 'verbose', 'debug', 'info', 'warn', 'error'. Default value is 'info'.

  • color - colorize logger messages. If this option is set to true then part of log message will be colorized to color which depends of log message level. Default value is true.

  • useDate - adds date in human readable format to log message. If this option is set to true then every log message begins with string (for example: [2015-03-28 04:25:56]) Default value is true.

API

Class methods:

  • setOptions - overrides default logger options. Attention! It overrides options for all logger instances (for all modules which requires logger module).
  • resetOptions - drops all options to their default values.
  • createLogger - create logger for given module. You can pass your module which requires logger and log message will contain last part of your module file path. It can be suitable for finding module by log message. If module value is omitted then logger own module will be taken.

Instance methods:

Creates and outputs log messages for different verbosity levels: Each method has the signature which is equal to methods of native Node console module. For example you can use formatted output:

logger.info('%s-%s', 'a', 1) //result (without prefix) will be: a-1
  • verbose - creates log message with 'verbose' verbosity level. Finally it calls itself console.log() method with generated message string.
  • debug - creates log message with 'debug' verbosity level. Finally it calls itself console.log() method with generated message string.
  • info - creates log message with 'info' verbosity level. Finally it calls itself console.info() method with generated message string.
  • warn - creates log message with 'warn' verbosity level. Finally it calls itself console.warn() method with generated message string.
  • error - creates log message with 'error' verbosity level. Finally it calls itself console.error() method with generated message string.

Also instance methods can be called in chain style, for example:

logger
   .info('hello world info')
   .debug('hello world debug')
   .warn('hello world warn')

Testing

Run tests:

npm run mocha

Run tests with istanbul coverage calculation:

npm run istanbul

Run codestyle verification (jshint and jscs)

npm run codestyle

Special thanks to:

  • Nikolay Ilchenko (http://github.com/tavriaforever)
  • Konstantinova Gela (http://github.com/gela-d)

Maintainer @tormozz48 Please send your questions and proposals to: [email protected]