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

log4js-wrapper

v1.3.2

Published

Custom wrapper to facilitate some common interactions with log4js

Downloads

80

Readme

log4js-wrapper

This is a wrapper around log4js-node to simplify the simple use-case. log4js has a lot of options I don't use and I always ended up writing shortcut methods to just log with different levels.

The logging output of log4js-wrapper depends on the set environment. In development or test environments, when logging, the filename and line number of the log will be output. Very useful for debugging.

In production environment, only the alias is used. This avoids generating an Error stacktrace everytime we log something (like it does in development or test envs).

If you supply a filename as a third parameter in the constructor, logs will also be saved in that file.

This package uses many ES6 features; therefore, you must be running Node v5.0.0 or above.

Usage

Minimalist example:

const Logger = require('log4js-wrapper');
const log = new Logger('debug', 'test-logging');

log.d('This is a debug level log');
log.t('This is a trace level log');
log.i('This is an info level log');

Which will output in development env:

[2015-10-23 10:21:29.756] [DEBUG] test.js:4 - This is a debug level log
[2015-10-23 10:21:29.761] [INFO] test.js:6 - This is an info level log

And in production environment:

[2015-10-23 10:22:26.552] [DEBUG] test-logging - This is a debug level log
[2015-10-23 10:22:26.557] [INFO] test-logging - This is an info level log

API

There are six methods, which correspond to the usual log4js log levels.

Here's an example using all methods:

const Logger = require('log4js-wrapper');
const log = new Logger('trace', 'test-logging');

log.d('This ia a debug level log');
log.t('This is a trace level log');
log.i('This is an info level log');
log.w('This is a warn level log');
log.e('This is an error level log');
log.f('This is a fatal level log');
log.i('This log should not be shown since the node process whill have been terminated by the fatal log');

And here's the output in development:

[2015-10-23 10:36:27.304] [TRACE] test.js:4 - This is a trace level log
[2015-10-23 10:36:27.309] [DEBUG] test.js:5 - This ia a debug level log
[2015-10-23 10:36:27.311] [INFO] test.js:6 - This is an info level log
[2015-10-23 10:36:27.311] [WARN] test.js:7 - This is a warn level log
[2015-10-23 10:36:27.311] [ERROR] test.js:8 - This is an error level log
[2015-10-23 10:36:27.312] [FATAL] test.js:9 - This is a fatal level log

IMPORTANT!

Please note that log.f() method exits the process. Only use this in the initial loading phase of your app.