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

nice-logger

v1.0.1

Published

Logger with levels and a nice format.

Downloads

12

Readme

nice-logger

A logger with levels and a nice format.

Example

var Logger = require("nice-logger");

var log = new Logger("main", "error");

try {
    log.debug("Uh oh.");
    /* Something dangerous. */
} catch (error) {
    log.error(error);  // Stack trace is automatically logged for Error objects.
}

Usage

Use it like log.<level>(arg1, arg2, ...). You can pass in as many arguments as you'd like. Anything that is not an Error or a String will be JSON stringified.

The logger normally writes to process.stdout. If any of the arguments is an Error object, the logger will write the whole message to stderr instead of stdout (so call error.toString() first if you'd like the logger to write to stdout.

Levels

The five allowed levels are, in descending order of priority:

  1. critical
  2. error
  3. warning
  4. info
  5. debug

You can (optionally) pass in a level as the second argument of the Logger constructor. This will set the default level. If you pass in something unrecognized, or don't pass in anything at all, the default level is set lower than debug. In other words, everything will get logged by default.

Methods

Logging methods:

  • #critical(...): Log a message at the critical level.
  • #error(...): Log a message at the critical level.
  • #warning(...): Log a message at the warning level.
  • #info(...): Log a message at the info level.
  • #debug(...): Log a message at the debug level.

Other methods:

  • #out(String): Write to process.stdout.
  • #err(String): Write to process.stderr.
  • #setLevel(level): Change the logger level.