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

@novivia/logger

v0.6.3

Published

Novivia event logger.

Downloads

13

Readme

Logger utility

Installation

yapm install

During the transition period from npm to yapm you can still do:

json5 -c package.json5

to generate the package.json file required by npm.

NEVER EDIT package.json DIRECTLY.

Usage

Log a message

var logger = require("logger")(module);

// Examples.
logger.log("info", "message");
logger.log("info", "message", {anything: "Meta data!"});
logger.info("possible to directly call the level on logger");
logger.warn("Supports %s.", "util.format()'s printf-like interpolation");

The log message will be prepended with the current date and time in the following format: YYYY-MM-DD HH:MM:SS. The timezone will be the local one when in development, UTC otherwise.

The log message will also display between brackets the name of the package inferred from the provided module object, to easily distinguish the emitter.

Note: Any uncaught exception will be caught by the logger, at which point it will display a detailed trace before exiting the application.

Logging levels

The following logging levels, in order of least to most critical, are allowed:

  • silly

    Something really really specific, about something already specific. Or something not really noteworthy, in any case. Most of the time it's better to not log it at all, otherwise it would just be silly.

  • debug

    Something pretty specific, but useful to have if having elementary problems. Most of the time this will log one iteration of a loop over a collection, for example.

  • verbose

    Something rather general about a portion of code, but that allows to understand what is the flow of an application when put together with other verbose calls.

  • info

    Something important to know about the application, but that is expected, informative and not negative.

  • warn

    Something for which a flag needs to be raised but that is not necessarily critical.

  • error

    Something critical that requires immediate attention.

By default the lowest level for which the logs are displayed is info, but that is lowered to verbose in a development environment. If required, the minimum level can be changed by doing the following:

var logger = require("logger")(module);

// Examples.
logger.debug("message"); // Will not display.
logger.setConsoleLevel("silly");
logger.debug("message"); // Will display.
logger.setConsoleLevel(); // Will revert to the default level for the
                          // original environment.

Keep in mind that multiple modules can be using this module simultaneously and a call to setConsoleLevel only affects the logger on which it is applied, use this to your advantage.