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

cf-logger-p

v6.0.0

Published

CF-Logger-Package contains Logging methods that can be utilized as a unified logging mechanism across all cf codebase.

Downloads

4

Readme

CF-Logger-Package

CF-Logger-Package contains Logging methods that can be utilized as a unified logging mechanism across all cf codebase.

Logging Levels

The supported logging levels are listed down based on priority.

  • error: 0
  • info: 1
  • debug: 2
  • warning: 3

Built With

Technologies & plugins used to create this application

Using This Private Repository as a Dependency

Prerequisites

1. Setup node & npm

This is an example of how to list things you need to use the application and how to install them.

1. Install the package

Install this package using the following command:

Then install your dependencies using the command
```bash
npm install cf-logger-package

Usage

// Import package
import LoggerOps from 'cf-logger-package'

// Create Logger instance & pass the logging level you want to set
const Logger = new LoggerOps('error')

//create a middleware function  to attach a traceid with reach API request
app.use(function (req, res, next) {
    Logger.setTraceId(uuidv4());
    next();
  })

// Use the following methods to log data
//Debug: The debug log should be created in the local & development environments. It should contain the information which will help developers to debug a problem. The following method can be used for the same:

Logger.logDebug(msg: string, obj: object)


//Error: The error log should be created in all environments in case of occurrence of an error. This can usually be implemented in the places where you are catching errors.The following method can be used for the same:

Logger.logError(msg: string, obj: object)

//Info: The info log should be created in the local & development environments. It should contain the information which will help developers to determine the current state of the application & informational statements regarding program execution. It can be used for application behaviour tracking. The following method can be used for the same:

Logger.logInfo(msg: string, obj: object)


//* Warning: The warning log should be created in the local & development environments. It should contain the information which will help developers to determine potentially harmful state of the application in real time but may not terminate the existing functionality or application processing.

Logger.logWarning(msg: string, obj: object)


// All the log methods accept two parameters :
// 1. Message:(dataType: string)
// 2. Metadata: (dataType: object) 

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.