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

poleno

v2.1.4

Published

A small and fast JSON logger

Downloads

43

Readme

CI Status Coverage Status

poleno

A small and fast JSON logger for Node.js applications, inspired by bunyan and bole.

Features:

  • 4 logging levels: debug, info, warn and error
  • logging functions accept a maximum of 2 arguments
  • logger can be created with a default properties object
  • child logger can inherit parent name
  • automatic parsing of Error objects
  • support for multiple streams

Usage

Installation:

npm install poleno

Configuration:

var poleno = require('poleno');

poleno.configure({
    streams: [
        { level: 'info', stream: process.stdout }
    ]
});

Creating a logger:

var log = poleno('FOO');
log.info('Foo', { foo: 'foo' });
// outputs: {"time":"2017-09-27T23:30:57.657Z","hostname":"debian","pid":"15491","name":"FOO","level":"info","msg":"Foo","foo":"foo"}

Creating a child logger

var childLog = log('BAR');
childLog.info('Bar', { bar: 'bar' });
// outputs: {"time":"2017-09-27T23:30:57.658Z","hostname":"debian","pid":"15491","name":"FOO:BAR","level":"info","msg":"Bar","bar":"bar"}

Viewer

A simple CLI log viewer is included:

node app.js | ./node_modules/.bin/poleno

API

poleno(name, [params])

Creates a new logger using the supplied name.

If the optional params object is provided then its properties will be included in every log message.

poleno.configure(options)

The options object can include the following properties:

  • {bool} fastTime - if set, time will be a number in milliseconds
  • {bool} flipArgs - if set, the log methods will accept ([params], message) as arguments instead, for compatibility
  • {array} streams - array of objects with level and stream properties

logger(name, [params])

Creates a child logger. The .name property on the log message JSON will be the parent name and name separated by the : character. If the name property is a falsy value then the child logger inherits parent name.

If the optional params object is provided then its properties will be included in every log message.

logger.trace|debug|info|warn|error(message, [params])

The message string will be assigned to .msg property on the log message JSON.

If the optional params is an object then its keys will be assigned to the log message JSON. If params is not an object then it will be assigned to a .data property on the log message JSON.

If params is an Error object then it will be assigned to an .error property on the log message JSON as an object with .code, .message and .stack properties. If params has a property that is an Error object then the property will be logged as an object in the same manner.

Also, see the flipArgs configuration option above.