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

printit

v0.1.20

Published

Dirty logging with class

Downloads

1,157

Readme

It began with a console.log...

You are probably like me, you always put some dirty logs in your software. You want to keep them dirty but you want fancy colors in your terminal, not in production, and you don't want to see this log displayed in your test output. At last, you don't care much about log level, the classical info/debug/warn/error is enough for you. Say welcome to printit the dirty logger with class!

Display rules

The way printit displays things is changed via environment variable:

  • Debug messages are not displayed.
  • When NODE_ENV is 'production', it doesn't display colors (it's better when you cat/tail a log file).
  • When NODE_ENV is 'test', it doesn't display logs (logs make mocha output looks less messy).
  • When DEBUG is 'true', it displays the debug messages.

Examples

var printit = require('printit');

var log = printit({
  prefix: 'my app',
  date: true
});

log.info("Print this with a blue info label and my app prefix and date");
log.debug("Print this with a green debug label and my app prefix and date");
log.warn("Print this with a yellow warn label and my app prefix and date");
log.error("Print this with a red error label and my app prefix and date");

log = printit({
  prefix: 'my app',
  date: false
});
log.error("Print this with a red error label and my app prefix");

log.error("Test 7");
log.error("Print this with a red error label");

Send logs to a file

It is possible to use a custom console, for example if you want to send logs to a file:

var fs = require('fs')
var Console = require('console').Console;
var printit = require('printit');

var out = fs.createWriteStream('log.txt');
printit.console = new Console(out, out);

var log = printit({
  prefix: 'my app',
  date: true
});

log.info("Print this with a blue info label and my app prefix and date");