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

lodge

v0.1.7

Published

Tiny logging engine

Readme

lodge

npm Bundle size Install size Donate

const log = require('lodge');

// simplest case
log('hello world');

// multiple arguments
log('hello', 'world');

// non-strings are pretty-printed
log('object:', { hello: 'world' });

// first argument can be a format string
log('string: %s, object: %O', 100, { hello: 'world' });

// join the given arguments into a formatted string
log.stylize('string: %s, object: %O', 100, { hello: 'world' });

// ansi colors included
log(log.red('CODE RED'));

// warnings
log.warn('be careful');

// print to stderr
log.error('oh crap');

// print a strack trace
log.trace();

// clear the console/terminal
log.clear();

// namespaces
const log2 = log.debug('foo');

// must set DEBUG=1 or DEBUG=foo to see this
log2('something useful in debugging');

// DEBUG=1 is not required to see warnings/errors
log2.warn('foo is deprecated');

// prefixes
log2.prefix('[foo]');
log2.prefix(() => `[${new Date().toISOString()}]`);

The built-in console functions are used when the global window variable exists. Otherwise, functions with similar behavior are used with the process.stdout or process.stderr streams.

You may override log.cleanStack to customize the output of the trace method.

Environment variables

Use QUIET=1 to disable all messages. The --quiet CLI flag also works.

The DEBUG environment variable is flexible. DEBUG=1 enables all debug logs. The asterisk (*) allows for globbing. For example, a* matches both abc and acb but not cba. The comma (,) lets you specify multiple globs. The --debug CLI flag is identical to DEBUG=1.

Use NO_COLOR=1 to disable ANSI colors. The --no-color CLI flag also works.

Use NO_WARNINGS=1 to disable warning messages. The --no-warnings CLI flag also works.

Use TRACE_WARNINGS=1 to attach a stack trace to each warning.

For browser environments, you can set these properties on the window object before importing this library.

Colors

The following ANSI colors are available: (256 color spectrum)

  • red
  • blue
  • green
  • yellow
  • cyan
  • pink
  • white
  • silver
  • gray
  • coal
  • black

The non-grayscale colors all have light variants available as lred, lblue, lgreen, etc.

Prefixes

You can set the prefix method of the main logger (or a namespace) if you want to prepend a string to every message.

const foo = log.debug('foo');
foo.prefix = () => `[${new Date().toISOString()}] foo:`

foo('test') // => '[2018-06-28T20:03:48.892Z] foo: test'

Loggers created by the create or debug method will inherit the prefix of their ancestors.

Loggers created with the debug method have a default prefix of their identifier with a dark gray color.