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

logwrangler

v2.0.0

Published

Wrangle up your logging

Downloads

22

Readme

logwrangler is a module logging system that you can easily extend to add various logging locations and functions.

Install

npm install --save logwrangler

Use

Logging to stdout

var logwrangler = require('../index');
var logger = logwrangler.create();

logger.log({
	level: logger.levels.INFO,
	ns: 'web server',
	message: 'some log message',
	data: {}
});

Options

level <string>

Specifies the level of the log. Levels can be found in logwrangler object or in the logger instance object.

Available levels include:

  • DEBUG
  • INFO
  • WARN
  • ERROR

ns <string>

Specifies a particular namespace for your log. Good for grouping logs by location in your codebase or by component.

node <string>

Name of the node, machine, or specific process currently running.

ident <string>

A more local identifier for the particular log. This could be something like a user ID to make it easy to trace the actions of a user.

message <string>

A human readable message to describe what is happening

data <object>

Contextual data related to the this particular log message. If the value of data is an Error(), the error will be parsed to grab it's message and stack trace and data will be rewritten to have an error property that will contain the contents of the Error object.

data, no error

{
	data: {
		someKey: 'someValue'
	}
}

data, with error

{
	data: new Error('Some error message')
}

// will become:

{
	data: {
		error: {
			message: 'Some error message',
			stack: <stack trace>
		}
	}
}

data, error and context

{
	data: {
		error: new Error('Some error message'),
		someKey: 'someValue'
	}
}

// will become

{
	data: {
		error: {
			message: 'Some error message',
			stack: <stack trace>
		},
		someKey: 'someValue'
	}
}

Custom logging handler

Creating a custom logger is as easy as providing an anonymous function to logger.use.

Parameters

options

Options that you passed in during initialization

	{
		options: {
			level: <level to use>
		}
	}

data

The data to be logged

{
	data: {
		level: <log level>,
		ns: <namespace - string>,
		ident: <custom identifier - string>,
		node: <node, machine, process, identifier - string>
		message: <message - string>,
		data: <custom data - object>
	}
}

Usage

var logger = fancyLog.create({
	level: fancyLog.levels.DEBUG, // default level to log
});

logger.use(function(options, data){
	
	// do something with your data
});