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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@codemaniac-technologies/codemaniac-logger

v1.0.1

Published

> CODEMANIAC Logger Class for microservice and application logging.

Readme

CODEMANIAC Logger

CODEMANIAC Logger Class for microservice and application logging.

Installation

  1. Install as an NPM package using the main brach of the codemaniac-logger git repository:
    npm install --save https://github.com/CodeManiac-Technologies-Pvt-Ltd/codemaniac-logger.git

Dependencies

  1. Node.js and NPM:

    As with all of our modules, node.js and npm must be installed prior to use. If you've yet to install node or would like a introduction, check out Introducation to Node.js on node's official site.

API

Class: CMTLogger

This class is used to create an instance of the codemaniac logger.

Constructor:

new CMTLogger();

Create a new logger object.

  • Returns: { CMTLogger}

STATIC logger.errorLogger {Object}

  • Generic winston logger.

STATIC logger.apiLogger {Function}

  • Request and Response logging Express middleware.

logger.config {Object}

  • Config object registered with the logger instance.

logger.logger {Object}

  • Initialized logger instance.

logger.debugWhiteList {Array}

  • When in debug mode, whitelist of filenames to allow logging.

logger.debugBlackList {Array}

  • When in debug mode, blacklist of filenames to prevent from logging.

logger.logMessage(level, payLoad, ctx={}, encrSchema=null, category=null, root=null)

Performs logging with encryption as defined in the config for the instance.

  • cronPattern {String|Date} - Valid cron pattern string (see http://crontab.org/) or Date object.
  • args {...*} - Arguments to passed to the jobFunction when executing

logger.init(paths, dirFilter, config, dataProtectService)

Updates the cronPattern or executation date for given job instance.

  • cronPattern {String|Date} - Valid cron pattern string (see http://crontab.org/) or Date object.

Usage

To use the logger, follow the below steps:

  1. Include the following in your application entrypoint file (usually index.js):
    'use strict';
    const CodemaniacLogger = require('codemaniac-logger');
    const logger = new CodemaniacLogger();
    scheduler.init(logConfig);

Tests

  1. To run the test suite, first install dependencies the run npm test

    npm install
    npm test
  2. Analyze code coverage:

    npm run test-coverage

    An HTML copy of the coverage report will be written to the ./coverage directory.

  3. Check adherance to style guidlines and detect potential problems:

    npm run lint
  4. Check for known security exploits of dependent packages:

    npm run security