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

replay-logger

v1.0.2

Published

Shareable Logger tool for all Replay project

Downloads

5

Readme

A Shareable Logger tool for all Replay project

Just a simple wrapper for node-bunyan

Environment variables

| Name | Description | Default | |--------------------|--------------------|--------------------| | NODE_ENV | Node Environment | development | | LOG_PATH | Log files path | $HOME/replay-logs (using process.env.HOME to get the user home directory) |

Installation

npm install replay-logger --save

Usage


// Init:
var ReplayLogger = require('replay-logger');
var logger = new ReplayLogger('serviceName');

// then use level name for logging, for example:
logger.trace('Some trace log message...');
logger.debug('Some debug log message...');
logger.info('Some info log message...');
logger.warn('Some warn log message...');
logger.error('Some error log message...');
logger.fatal('Some fatal log message...');

// you can also use 'log' function for logging info level
logger.log('Some info log message...');

// You can also use format for msg formatting.
logger.info('hi %s', 'bob');

// First field can optionally be a "fields" object, which is merged into the log record.
logger.info({foo: 'bar'}, 'hi');

// Special case to log an `Error` instance to the record.
// This adds an "err" field with exception details (including the stack) and sets "msg" to the exception message.
log.info(err);  
logger.info(err, 'more on this: %s', 'some more info');


// To pass in an Error and other fields, use the `err` field name for the Error instance.
log.info({foo: 'bar', err: err}, 'some msg about this error');

Extra Info:

level-suggestions