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 🙏

© 2024 – Pkg Stats / Ryan Hefner

kth-console-log

v1.2.2

Published

Small console library used as default logger in KTH npm packages

Downloads

13

Readme

NPM

kth-console-log

Simple console logger used for default logging in our npm packages

This module can be use as a default, node-bunyan compatible logger in projects where basic logging that should be overridable should be available.

Requirements of overriding logger

If you use kth-console-log in your module and want to replace it with a custom logger, just make sure that the logger you are providing adheres to the following pseudo interface:

function trace(...args)
function debug(...args)
function info(...args)
function warn(...args)
function error(...args)
function fatal(...args)

Example of usage

In the module that should have an overridable logger add:

const defaultLogger = require('kth-console-log')
var log = defaultLogger

Then export a getter/setter for the logger along with everything else that should be exported from the module:

  return {
    funcToExport: function() { ... },
    get logger() {
      return log
    },
    set logger(logger) {
      log = logger
    }
  }

Then log as usual in the module itself:

log.info('This is some info-level logging')

And in the main application that depends on the module just override the exported logger with your own logging object:

var myModule = require('my-module-with-overridable-logging')
var myLogger = require('my-initialized-logger')
myModule.logger = myLogger