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

hlogger

v0.0.9

Published

Yet another logger

Downloads

5

Readme

Simple log system

var log = require('hlogger').createLogger("name");

log.info("test");

Initial relase

Simple pet project that contains ways to create new Writers, Adapters

Logger

The way developer issues logging

	log.info("info log");
	log.error("error log");
	log.warn("warning log");
	log.verb("verbose log");

Adapter

Log filtering, adapters can be created to receive only error, warning logs

Writer

Attached to adapter, writers will be responsible to write the logs either files, console, sql, socket

Right now only two predefined loggers availalbe: file and console

Log formats

Formats for adapters:

  • %m - The actual message
  • %c - logWriter count
  • %l - TAG name [ERROR,WARN,INFO,VERBOSE]
  • %n - Logger name
  • %e - Ellapsed time per writer
  • %E - Ellapsed per Logger
  • %t - Date string
  • %a - Ascii escape char
  • %% - Literal '%'
  • %| - Special case, all chars after %| will be presented on the right

Config format:

Simple:

{
  "writers":{
    "myconsole": {
      "writer":"console"
    }
  },
  "loggers": {
    "main":["ERROR","VERBOSE","INFO","WARN"]
  },
  "adapters" : [
    {
	  "levels": ["INFO","VERBOSE","WARN","ERROR"],
      "writers": ["myconsole"],
      "loggers": {
        "Hello": ["INFO"],
        "main": ["ERROR"]
       }
    }
  ]
}

Create a set of writers, and setup adapters using those writers

{
  "writers" : {
    "filetolog":{
      "writer":"file",
      "opts":{
        "path":"access.log"
      }
    },
    "errorfile": {
      "writer":"file",
        "opts": {
          "path":"error.log"
        }
      },
    "console1": {
      "writer":"console",
      "opts":{
        "format":{
          "ERROR":"-------------- ERR %m -----------------"
        }
      }
    },
    "console": {
      "writer":"console"
    }
  },
  "adapters" : [
    {
      "levels": ["INFO","VERBOSE"],
      "writers": ["filetolog","console"]
    },
    { 
      "levels":["ERROR","WARN"],
      "writers": ["errorfile","console1"]
    }
  ]
}