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

personalized-logger

v1.17.0

Published

It is personalized method to Log messages in both console and file. The first version contemplates a simple idea of logging using the below formatting:

Readme

Personalized Logger

It is personalized method to Log messages in both console and file. The first version contemplates a simple idea of logging using the below formatting:

timestamp - Level - SubLevel - Machine Hostname - Process ID - Conversation ID: content

Levels

  • SYSTEM - It contemplates how the system works;
  • ENDPOINT - It contemplates the health of the application endpoints when it receive requests and send responses;
  • BUSINESS - It contemplates the business rules in the application;

Sublevels

It contemplates what kind of information exists in each Level.

  • INFO;
  • WARN;
  • ERROR;

How to use Personalized Logger

First step - Installing:

npm i --save personalized-logger

Second step - Adding the component:

const Logger = require("personalized-logger");

or

import Logger from "personalized-logger";

Third step - Using in application:

Logger.system(`${conversationID}`, `${contentMessage}`, `${subLevel}`);
/*
* this is a simple example using SYSTEM level logging but in all levels function 
* the same parameter are used
*/

How to call each level of log

Each level logging is represented by a function with the name of the level, in the above example, we used SYSTEM as a level but you can do with the other ones like the below examples:

Logger.endpoint(`${conversationID}`, `${contentMessage}`, `${subLevel}`);

or

Logger.business(`${conversationID}`, `${contentMessage}`, `${subLevel}`);

All functions receive the same three parameters:

  • conversationID - The ID of the conversation that is currently using our application;
  • contentMessage - A message defined by the user (DEV) to define the context of the log itself;
  • subLevel - The default sublevels listed before, the default sublevel is INFO;