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 🙏

© 2025 – Pkg Stats / Ryan Hefner

get-log

v1.1.5

Published

Logging utility, easy to use and ready for production

Readme

get-log

Node.js Logging Utility, easy to use and ready for production.

Installation

$ git clone --branch=master git://github.com/enricostara/get-log.git
$ cd get-log
$ npm install

Coding

var getLogger = require('get-log');

getLogger.PROJECT_NAME = 'my-best-app';
// or better: getLogger.PROJECT_NAME = require('./package.json').name;

var logger = getLogger('awesome-name');

logger.info('Let\'s start!');

logger.debug('Current file is %s', __filename);

var uglyLogger = getLogger('ugly-name');

uglyLogger.warn('This a Warning! Next debug log could not be displayed..');

uglyLogger.debug('Please, don\'t print me!');

uglyLogger.error('I\'m an error log, isn\'t it?');

Execution

Set DEBUG env to configure what logger (by name) can log at debug level. Use * as wildcard and use - as name prefix to exclude; the values are comma separated.

$ DEBUG=*,-*ugly-name node example.js 

Output

[my-best-app:awesome-name] debug is ENABLED
[INFO] Thu, 30 Oct 2014 00:16:43 GMT my-best-app:awesome-name Let s start!
[DEBUG] Thu, 30 Oct 2014 00:16:43 GMT  my-best-app:awesome-name Current file is /example.js 
[WARN] Thu, 30 Oct 2014 00:16:43 GMT my-best-app:ugly-name This a Warning! Next debug log could not be displayed..
[ERROR] Thu, 30 Oct 2014 00:16:43 GMT my-best-app:ugly-name I m an error log, isn t it?

Unit Testing

$ npm test

Dependencies

  • colors: get colors in your node.js console

  • debug: tiny node.js and browser debugging utility for your libraries and applications

License

The project is released under the MIT license