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

tlog

v0.2.4

Published

Simple Node.js logging with extra features

Readme

tlog

tlog tries to provide a simple logging system with extensive tag system. Tags are used for filtering log output. tlog uses hierarchical tags to group multiple tags in one.

Install

$ npm install tlog

Usage

var tlog = require('tlog');

// create loggers

var logA = tlog('logA');
var logB = tlog('logB');

logB.level = tlog.Level.WARNING; // aka. 30

logA.d('Hello, Debug!');
logA.i('Hello, Info!');
logA.w('Hello, Warning!');
logA.e('Hello, Error!');

tlog.level = tlog

logB.d('Hello, Debug!');
logB.i('Hello, Info!');
logB.w('Hello, Warning!');
logB.e('Hello, Error!');

// silence messages from logA
logA.level = tlog.Level.SILENT; // aka. 9999

logA.e('This wont log');

Configs

To use per application configs, put tlog.json in application path. Config file is searched from all applications parent folders.

Last best matching tag from config is used. This enables to set configs for a set of tags at once.

Log levels can have the name or the actual numeric value.

Example config:

{
	"level": "warning", // global log level
	"tags": { // per tag configs
		"log": { // matches everything starting with 'log'
			"level": "debug"
		},
		"logB": { // matches everything starting with 'logB'
			"level": 10
		}
		"logC": {
			"level": null // use global level
		}
	}
}

Log levels

You can use any integer value as a logging level. Here are predefined values.

tlog.Level.DEBUG = 10;
tlog.Level.INFO = 20;
tlog.Level.WARNING = 30;
tlog.Level.ERROR = 40;
tlog.Level.SILENCE = 9999;

Log level options

tlog.Level.options contains the console printing options for each log level.

// create new log level
var PRE_WARNING = 25;
tlog.Level.options[PRE_WARNING] = {
	name: 'pre-warning',
	color: {
		text: 'red',
		background: 'yellow'
	}
};

Writers and formatters

not yet implemented/designed fully