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

v1.0.0

Published

A logging framework that allows injection of custom logging strategies as a means to configure logging.

Downloads

26

Readme

c4cc-logging

This module provides a pluggable logging framework by allowing different logging strategies to be injected. This will allow consumers to swap logging strategies in and out of a consuming module with minimal changes.

installation

TBD

usage

Minimalist

const {C4CCLogging} = require('c4cc-logging');

const logManager = new C4CCLogging();

const logger = logManager.getLogger();

logger.error('error log message');
logger.warn('warn log message');
logger.info('info log message');
logger.debug('debug log message');
logger.log('default log message'); //generic log() uses info() for ConsoleLoggingStrategy 

The default logging strategy if none is specified is in the internal ConsoleLoggingStrategy.

custom logging strategies

The logging strategy and default logging level can be specified in the constructor. The default logging level is the level that new loggers will be created with if no level is specified in the call to getLogger();

const {C4CCLogging, LEVELS} = require('c4cc-logging');
const myLoggingStrategy = ...;
const logManager = new C4CCLogging(myLoggingStrategy, LEVELS.warn);
const defaultLogger = logManager.getLogger();  // this logger will use the default specified above - LEVELS.warn
const logger = logManager.getLogger('my-log-component', LEVELS.debug); // log all messages from this particular logger since it overrides to LEVELS.debug.

Usage of Log4JS is supported via the c4cc-logging-log4j module - see the c4cc-logging-log4js README.md for more info.

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();