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

log-hanging-fruit

v0.4.0

Published

The simplest possible log that could possibly work

Downloads

7

Readme

log-hanging-fruit

The simplest logger that could possibly work.

This logger supports logging messages to multiple destinations. It comes with two loggers built-in that can log to the console or to a text file.

There are 4 functions that can be used to log, each of them maps to the severity of the message being logged: debug, info, warn, or error. See example below.

sample of use

// Require the logger an initialize it
var logger = require('./logger').logger;
var consoleAppender = require('./consoleAppender');
var fileAppender = require('./fileAppender');
var options = {filePath: __dirname + '/' };
logger.setup(options);

// Wire up both appender (console and text file) to be
// notified when something needs to be logged.
logger.on('log', consoleAppender.log);
logger.on('log', fileAppender.log);

// Log a few things with different levels
logger.debug('hello debug world');
logger.info('hello info world');
logger.warn('hello warning world');
logger.error('hello error world');

limitations

The built-in loggers don't include any advanced features like color logging (to the console) or rolling files after a size has been reached. This logger is inspired in a way from log4net in the sense that it supports multiple loggers (called appenders in log4net lingo) and supports multiple levels but this logger is not nearly as battle tested as log4net or any of the other famous node.js loggers like winston.