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-config

v0.1.1

Published

A simple common configuration library for log4js

Downloads

276

Readme

log4js-common-config

This module aims to standardize application logging configuration in Node.js with log4js (https://github.com/nomiddlename/log4js-node) by providing a standard (configurable) naming convention and location for external log4js configuration files.

The advantage is that one single configuration file would be used to customize and control log4js, rather than different modules providing their own log4js settings, configuration and files.

How to use

Add the following dependency to your package.json, and then run npm update:

"dependencies": {
    ...
    "log4js-config": ">= 0.1.0",
    ...
}

The log4js-common-config dependency will automatically pull log4js for you so no further dependencies are explicitly needed.

Logging

Add the following module import statement at the top of the entry point of your application:

var logger = require("log4js-common");

This will automatically configure logging in your application using a file called app-logging.json, which should follow log4j's logging configuration file structure: https://github.com/nomiddlename/log4js-node#configuration. This file can either be placed in the root folder of your application, or in a folder called config.

In order to retrieve a logger, use the get method followed by a log category name:

var log = loger.get("some.log.category.name");
log.debug("debug message");
log.info("info message");

Log4js will be automatically configured according to the contents of your app-logging.json configuration file.

Using non-standard configuration

If for some reason the default configuration is not sufficient, it is possible to provide the module with a function that will return the correct name and location of the log4js configuration file using the module's init method:

var logger = require("log4js-common").init(function() {
    return("./settings/logging-config.json");
});

It is only necessary to do this once, preferably near or at the very top of the entry point to your application. Subsequent calls to require("log4js-common") will use the non-standard configuration automatically.

Testing

Basic unit testing is provided via Grunt and nodeunit:

grunt test