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

mlogy

v1.0.3

Published

interface for creating log records

Downloads

13

Readme

mlogy

NPM Version Build Status Coverage Status

Interface for creating log records

Installation

npm install --save mlogy

Usage

The modules assumes loggers are organized in a tree tracked by the parent attribute however this is managed outside the implementation of the logger.

Logger(context, name, [level])

  • context

    The context contains the shared settings shared between all loggers in a system. The context is stored as context on the logger and is allowed to change during the life time of the logger to allow loggers created by libraries to be assimilated into a bigger application logger hierarchy

    • defaultProcessors

      A List of processors; functions that accepts a record and somehow modifies it by e.g attaching extra data

    • proxy

      A proxy through which all records should be sent.

  • name

    The name of the logger. By convention a dot.separated.string

  • level

    The minimum level the logger will process records for as either a numeric value or a named level from standard-levels. If undefined the level of the parent logger is used.

var Logger = require('mlogy')
  , ctx = {defaultProcessors: []}
  , root = new Logger(ctx, '', 'ERROR')
  , other = new Logger(ctx, 'other', 'DEBUG')

other.parent = root

setLevel

Update the minimum level the logger will process records for

trace(frmt, ...)

debug(frmt, ...)

info(frmt, ...)

warn(frmt, ...)

error(frmt, ...)

critical(frmt, ...)

Send a message at the indicated level