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 🙏

© 2026 – Pkg Stats / Ryan Hefner

logro

v0.1.16

Published

Handy logger impl.

Readme

:tada: logro NPM version codecov Build status

Handy logger impl.

Built on-top of bole to provide ready to use logging:

const log = require('logro').createLogger(__filename);
log.info('Just testing');

It also comes with simple formatter for the CLI:

$ echo '{"foo":"bar","time":1560577967962}' | logrof
#  12:52:47  { foo: 'bar' }

How it works?

By design, logro messages are sent to the stderr:

$ node main.js 2>&1 | logrof
#  1:22:37  INFO main.js { hostname: 'dev.local', pid: 62525, evt: 'Just testing' }

Most methods receive a message and some data, otherwise an error with some data, etc.

Last argument is used as identity for the ongoing message, on all methods.

Quiet methods (derived from bole):

  • info(msg[, data[, guid]]) — Just info; hidden on production
  • debug(msg[, data[, guid]]) — Debug info; shown during test only
  • warn(msg[, error[, guid]]) — Relax warnings; hidden from stdout
  • error(msg[, error[, guid]]) — Regular/relax errors; not critical, hidden

If warn/error receives an instance of Error, a proper failure/exception will be raised, respectively.

Loud methods:

  • failure(err[, type[, guid]]) — Real warnings!
  • exception(err[, msg[, data[, guid]]]) — Fatal errors :bomb:

Both methods always print to the stdout during development to help, the default level is info.

Log levels are set as follows:

  • process.env.NODE_ENV === 'production' — set error level
  • process.env.NODE_ENV === 'test' — set debug level
  • process.env.REMOVE_LOG === 'true' — disable all logs

Formatting

Pipe your logs to logrof in order to give them some format, it will ignore non JSON objects from the stream.

Recognized fields are: ts, time, ns, name and level.

Options:

  • --quiet — Non JSON objects are not longer printed
  • --no-color — Disable colors on formatting from output

Otherwise, the default output is JSON, always.

Public API

  • new Logro(name) and Logro.createLogger(name) — Creates a new logro instance, name can be a filepath.
  • Logro.setForbiddenFields(fromConfig) — List of fields to be ignored from data objects; also Logro.clean() is affected by this.
  • Logro.getExpressLogger() — Returns a middleware function for easy logging, it also setup req.log as helper.
  • Logro.getLogger(name) — Returns a bole instance.
  • Logro.format(message[, data[, now]]) — Returns the message formatted for CLI usage: [timestamp] [message] (data is optional)
  • Logro.logger(message) — Print formatted messages to the stdout.
  • Logro.inspect(message) — Print formatted messages to the stdout; ignored if process.env.NODE_ENV === 'test'
  • Logro.clean(data[, fields]) — Safely clone and remove fields from any given object, it also removes those set by setForbiddenFields() calls.