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

lib-logging

v1.2.0

Published

A node.js logging implementation.

Readme

lib-logging

Test Publish

A node.js logging implementation.

Installation

npm install --save lib-logging

Usage

Example

const logging = require('lib-logging')
logging.log(1, 'server', 'Hello World')
// will log in console (and file):
// [NOTE - SERVER | Thu Feb 04 2021 21:13:16 GMT+0100 ] Hello World

If you would like to log also the origin of the message you can use:

const logging = require('lib-logging')
logging.log(1, 'server', 'Hello World', true)
// will log in console (and file):
// [NOTE - SERVER | Thu Feb 04 2021 21:13:16 GMT+0100 ] (/my/path:35 - myFunction) Hello World

By default lib-logging will store all loggings in ./logs/lib-logging.log. You can disable this feature by using the addOptions() function (see configuration for more details).

Possible parameters

The log() function takes four arguments.

  1. level: The log level as number (1: Note, 2: Warning, 3: Error)
  2. service: The corresponding service triggering the log function, by default ['server', 'cors', 'redis', 'lifesign', 'mariadb'] are possible values
  3. msg: The message string to log
  4. caller: Boolean value (default false) which provides additional information about the origin

Configuration

To modify the default values of lib-logging you can use the addOptions(options) function.

const options = {
  enableLogging: false,
  logToFile: {
    note: false
  },
  level: {
    debug: 4
  },
  services: ['my service'],
  globalCaller: false
};
log.addOptions(options);

By default all events will be loged in the file ./logs/lib-logging.log. You can disable this feature for each loglevel individual, by setting the property in logToFile to false or disable the whole feature globally by setting enableLogging to false.

// disable on loglevel
logging.addOptions({
  logToFile: {
    note: false
  }
});
// disabled on NOTE events
// disable globally, good idea by using lib-logging in a browser application
logging.addOptions({
  enableLogging: false
});

For debugging purposes, you can set the globalCaller property to true. This will ptovide the additional caller information on all log events.