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

node-custom-console

v0.2.4

Published

Custom console for nodejs

Readme

node-custom-console

NPM version Build Status Coverage Status dependency Status devDependency Status

Custom console for Node.js log.

Usage

Just replace your console with this module.

var console = require('node-custom-console')('module1');
console.log('foo', 'bar')
// > 2014-10-02T06:15:16.830Z [log] 44999 module1: foo bar

var console = require('node-custom-console')('module2');
console.info('foo', 'bar')
// > 2014-10-02T06:15:16.830Z [info] 44999 module2: foo bar

Debug Target

You can specify the debug targets.

process.env.NODE_DEBUG='module1'

var console = require('node-custom-console')('module1');
console.log('foo', 'bar')
// > 2014-10-02T06:15:16.830Z [info] 44999 module1: foo bar

var console = require('node-custom-console')('module2');
console.info('foo', 'bar')
// No output

You can also set multiple targets with module1,module2 and all with *.

Debug Level

You can specify the debug levels.

process.env.NODE_DEBUG='module1:info'

var console = require('node-custom-console')('module1');
console.log('foo', 'bar')
// No output

console.info('foo', 'bar')
// > 2014-10-02T06:15:16.830Z [info] 44999 module1: foo bar

Here is the priority order of available levels. log < info < warn < error

Custom Formatter

Furthermore, you can use custom formatter as below.

var console = require('node-custom-console')('module1', formatter: function() {
  var args = [];
  args.push(this.tag + '-' + this.severity);
  args = args.concat([].slice.call(arguments, 0));
  args.push(';');
  return args;
});
console.info('foo', 'bar')
// > chai-info foo bar ;

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

Copyright

Copyright (c) 2014 Daisuke Taniwaki. See LICENSE for details.