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

c4cc-logging-log4js

v1.0.1

Published

Provides a logging strategy, Log4JSLoggingStrategy, that can be injected into the c4cc-logging framework to configure log4js.

Downloads

3

Readme

c4cc-logging-log4js

This module provides a logging strategy for the c4cc-logging framework that uses log4js-node.

installation

TBD

usage

Minimalist

const {C4CCLogging, LEVELS} = require('c4cc-logging');
const Log4JsLoggingStrategy = require('c4cc-logging-log4js');

const log4JSStrategy = new Log4JsLoggingStrategy();
const logManager = new C4CCLogging(log4JSStrategy);
const defaultLogger = logManager.getLogger();

The default strategy uses the default log4JS appender which is the console.

The Log4JsLoggingStrategy accepts a standard log4js configuration object in the constructor which will allow for module specific configuration of logging.

const {C4CCLogging, LEVELS} = require('c4cc-logging');
const Log4JsLoggingStrategy = require('c4cc-logging-log4js');

const log4JSStrategy = new Log4JsLoggingStrategy({
  appenders: {c4cc: {type: 'file', filename: 'c4cc.log'}},
  categories: {default: {appenders: ['c4cc'], level: 'error'}},
});
const logManager = new C4CCLogging(log4JSStrategy);
const c4ccLogger = logManager.getLogger('c4cc');
const customModuleLogger = logManager.getLogger('my-custom-module-logger', LEVELS.DEBUG);  //creates a log4js logger which will use the default category with level set to DEBUG so that everything will be logged

The example above will log to a flat file, c4cc.log by default instead of the console, and specifies that only error or higher messages should be logged.

See the log4js-node README for more information on log4js capabilities: https://github.com/log4js-node/log4js-node/blob/master/README.md