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

@mter/lazy-logger

v0.0.4

Published

simple console logger insterface to improve performance by lazy string evaluation

Downloads

264

Readme

@mter/lazy-logger

Simple console logger to improve performance with lazy string evaluation.

How to use

Control the logging with levels


/**
 * the log level is taken from the env variable "_LOG_LEVEL"
 * log level could be any integer between 0 - 50
 *   TRACE = 0,
 *   DEBUG = 10,
 *   INFO  = 20,
 *   WARN  = 30,
 *   ERROR = 40,
 *   SEVERE = 50
 */

// _LOG_LEVEL = 20

import { LOGGER } from "@mter/lazy-logger"

LOGGER.severe(()=>"This is my severe log message") // print "This is my severe log message"
LOGGER.error(()=>"This is my error log message") // print "This is my error log message"
LOGGER.warn(()=>"This is my warning log message") // print "This is my warning log message"
LOGGER.info(()=>"This is my info log message") // print "This is my info log message"
LOGGER.debug(()=>"This is my log message") // print nothing
LOGGER.trace(()=>"This is my log message") // print nothing

Change what's printed depending on the current log level


LOGGER.info((loglevel) => {
  if (loglevel < LEVEL.INFO)
    return [
      "This is my special message when log level is info",
      {
        /* some details object */
      },
    ];
    return ["This is my default message"]
});

Set log level programatically

import { LOGGER, LEVEL } from "@mtr/lazy-logger"

...

LOGGER.setLogLevel(LEVEL.DEBUG); 

Check is a given log level is loggable with current logger configuration

import { LOGGER, LEVEL } from "@mtr/lazy-logger"

...
// check if DEBUG logs are loggable. If the current log level is higher than DEBUG. this will return false;
const isDebugLoggable: boolean = LOGGER.isLogLevelLoggable(LEVEL.DEBUG);