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

@libertyio/log-node

v0.1.1

Published

Write messages to stderr and stdout

Downloads

4

Readme

Introduction

NOTE: the library has been renamed to @libertyio/log-node-js

Write messages to stderr and stdout. Features include:

  • configurable color scheme, e.g. use red for error messages
  • configurable tag to prefix each message, e.g. [label] message
  • configurable output filters, e.g. hide trace level messages

Example:

const { Log } = require('@libertyio/log-node-js');
const log = new Log();
log.error('an error message');
log.warn('a warning message');
log.info('an info messsage');
log.ok('a success message');
log.trace('a trace message');
log.print('raw output without a log level');

Application wrapper

If you're writing a NodeJS application and you need to use the log module from many components, you probably don't want to repeat the same code in each module to configure the log.

Here is a NodeJS example of writing a wrapper module that you can use throughout your application:

const { Log } = require('@libertyio/log-node-js');

const { LOG_LEVEL } = process.env;

let level = LOG_LEVEL || 'info';
let stream = process.stderr;
let log;

switch (level) {
    case 'error':
        log = new Log({ tag: 'MY_APP', enable: { error: true, warn: false, info: false, ok: false, trace: false, print: true }});
        break;
    case 'warn':
        log = new Log({ tag: 'MY_APP', enable: { error: true, warn: true, info: false, ok: false, trace: false, print: true }});
        break;
    case 'info':
        log = new Log({ tag: 'MY_APP', enable: { error: true, warn: true, info: true, ok: true, trace: false, print: true }});
        break;
    case 'trace':
        log = new Log({ tag: 'MY_APP', enable: { error: true, warn: true, info: true, ok: true, trace: true, print: true }, stream });
        break;
    default:
        // if enviornment contains invalid log level, default to info and display a warning
        log = new Log({ tag: 'MY_APP', enable: { error: true, warn: true, info: true, ok: true, trace: false, print: true }});
        log.warn(`invalid log level selected: ${level}`);
        break;        
}

export {
    log,
};

Then in your application you just do this:

const { log } = require('your_wrapper');
log.info('an info messsage');

So you can change the log level everywhere by setting the environment variable LOG_LEVEL before you start the application.