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

loglet

v0.2.0

Published

A simple logger.

Readme

Loglet - A Simple Logger.

Loglet is a simple configurable logger that can be configured to conditionally log a particular output. This is especially useful to be combined with command line parameter (or configuration files) to determine the output you are logging.

The scenario loglet is designed for is for people who use console.log to trace through the program and has to frequently comment/uncomment them to see the different parts. By using loglet you can leave the programs to be and just enable/disable the comments by passing in settings, which are treated as regular expressions.

Install

npm install loglet 

Usage

var logger = require('loglet');

logger.setKeys(['main', 'test']); // used to determine what to log. 

logger.debug('main.first', 'hello world - this will be logged'); 

logger.debug('test.first', 'this will also be logged');

logger.debug('skip.me', 'this will not be logged');

logger.error({error: 'stuff_happens', description: 'Errors will also be logged'});

Desciption

Do you use console.log to trace and debug the output of the program? If you do you'll find console.log is littered throughout the code, but you'll have to constantly go back and forth to comment/uncomment out the logging. Loglet is a replacement for those logging calls that allows you to leave those code alone but you can turn them on/off based on settings you pass in for the program.

Let's say you use either optimist or yarg to parse the command line. You can then collect the debug arguments as follows:

var argv = require('yargs')
  .alias('d', 'debug')
  .argv;

var logger = require('loglet');

logger.setKeys(argv.d);

logger.debug(...); // logger.debug is the main function that you'll use for conditional logging. 

...

To change what's being logged, just pass in different sets of keys through the command line. The keys are regular expressions, so you can have fine control over what's actually logged.

program -d main -d test\\.