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

glogg

v2.2.0

Published

Global logging utility

Downloads

6,850,806

Readme

glogg

NPM version Downloads Build Status Coveralls Status

Global logging utility.

Usage

var getLogger = require('glogg');

var logger = getLogger('my-namespace');

// logs strings
logger.debug('The MOST verbose!');
logger.info('Some important info');
logger.warn('All the warnings to you');
logger.error('OH NO! SOMETHING HAPPENED!');

// supports util.format!
logger.info('%s style!', 'printf');

// log anything
logger.debug({ my: 'obj' });
logger.info([1, 2, 3]);

// somewhere else
logger.on('info', function (msg) {
  // do something with msg
});

// must be handled to avoid crashing process
logger.on('error', function (msg) {
  // now it won't crash
});

API

Note: This module makes no assumptions about the log levels and they will always be emitted. If you are looking to filter some out, your listeners will need to have extra logic.

getLogger([namespace])

Create a new logger at the given namespace (or the default if no namespace is provided). Returns an augmented sparkles EventEmitter object with 4 methods: debug(), info(), warn() and error(). When called, these methods emit an event with the same name. If the first argument is a string, the arguments are passed through node's util.format() before being emitted. Other parts of a node program can get the logger by namespace and listen for the events to be emitted.

logger.debug(msg, ...args)

Emits a debug event with the given msg.

If the first argument is a string, all arguments are passed to node's util.format() before being emitted.

If the first argument is not a string, all arguments will be emitted directly.

logger.info(msg, ...args)

Emits a info event with the given msg.

If the first argument is a string, all arguments are passed to node's util.format() before being emitted.

If the first argument is not a string, all arguments will be emitted directly.

logger.warn(msg, ...args)

Emits a warn event with the given msg.

If the first argument is a string, all arguments are passed to node's util.format() before being emitted.

If the first argument is not a string, all arguments will be emitted directly.

logger.error(msg, ...args)

Emits a error event with the given msg.

If the first argument is a string, all arguments are passed to node's util.format() before being emitted.

If the first argument is not a string, all arguments will be emitted directly.

Note: You must handle this event in some way or the node process will crash when an error event is emitted.

logger.on(event, fn)

Standard API from node's EventEmitter. Use this to listen for events from the logger methods.

License

MIT