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 🙏

© 2025 – Pkg Stats / Ryan Hefner

logification

v1.0.1

Published

Simple logger

Readme

logification

Simple logger using console.log(), console.group(), some funky ASCII, coloring and custom delimiters - supports log-levels acc. to RFC5424.

Simple logger using console.log(), console.group() and some funky ASCII, please note that additionally to the severity-level according to RFC5424, another distinction is made here via 'type' This allows better fine-tuning of the logger. Lets assume you encounter a warning (level 4), but you still want to display the console-log with an error-decoration in some special cases in order to draw attention when looking at the log, you can use the type 'err'.

To additionally write the log to file, set the value for 'writeToFile' in 'loggly-config.json' to true and set the correct path for 'logFileLocation'

//      .------.     _______________ 
//     /  _)  __\   |  E R R O R !  |
//    |      ( )/   |_  ____________|
//     \___     \     |/
//         ``||||      

INFO:

Installation:

npm i logification --save

Logging levels/priorities according to RFC5424:

| Level | priority | |---|---| | emerg | 0 | | alert | 1 | | crit | 2 | | error | 3 | | warning | 4 | | notice | 5 | | info | 6 | | debug | 7 |

Logging states of the app in './loggly-config.json' (can be changed at runtime):

| Logging-state | behaviour | |---|---| | verbose | Log msgs of all priorities (0-7) | | normal | Log msgs of the priorities 0-4 | | silent | No logging at all |

Logging source-types (adapt/extend as needed):

Log-statement sources can be added/edited/removed, will be shown with source-specififc delimiters for differentiation.

| Source | Explanation | |---|---| | db | database related msgs | | app | main app module related msgs | | route | route related msgs | | mqtt | mqtt related msgs |

Usage Example

In this case we are logging an error if the env-vars can't be required, calling loggly with three arguments (msg, level, source).

const dotenvAbsolutePath = path.join(__dirname, '.env');
const dotenv = require('dotenv').config({
  path: dotenvAbsolutePath
});
if (dotenv.error) {
  loggly.error(`ERROR WHILE READING ENV-VARS: \n${dotenv.error}`, 'err', 'app.js');
  throw dotenv.error;
}