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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@maksims/logger.js

v2.1.3

Published

Small and simple logging library to log the information in to files and console.

Downloads

257

Readme

logger.js

Small and simple logging library to log the information in to files and console.

Table of Contents

Documentation

Installation

npm i @maksims/logger.js

Creating a logger

import Logger from "@maksims/logger.js";

export const logger = new Logger<"dev" | "prod">({
  // By setting "mode", we can filter out exactly what needs to be logged.
  // For example, when the "mode" has value "dev" only log calls that use
  // "dev" filter will be executed.
  mode: process.env.MODE,
  file: {
    //  With this option we set the dir path in which the log files will be served.
    dirPath: `${process.cwd()}/logs`
  }
});

Log into console and file

import { logger } from "index.js";

function doStuff() {
  // ...do stuff

  // This info messages will be logged only in "dev" mode!
  logger.in(["dev"]).console.info("info:dev");
  // This warn messages will be logged only in "prod" mode!
  logger.in(["prod"]).console.warn("warn:prod", { code: 400 });
  // This error messages will be logged  in both "dev" and "prod" mode!
  logger.in(["dev", "prod"]).console.error("error:dev:prod", [1, 2, 3]);
  
  // ...do stuff
};

doStuff();
import { logger } from "index.js";

function doStuff() {
  // ...do stuff

  // This info messages will be logged only in "dev" mode!
  logger.in(["dev"]).file.info("info:dev");
  // This warn messages will be logged only in "prod" mode!
  logger.in(["prod"]).file.warn("warn:prod", { code: 400 });
  // This error messages will be logged in both "dev" and "prod" mode!
  logger.in(["dev", "prod"]).file.error("error:dev:prod", [1, 2, 3]);
  
  // ...do stuff
};

doStuff();

You can call log function directly without filter to log specific information in any mode.

import { logger } from "index.js"

logger.console.info("This message will be logged in any mode!");

Custom prefix color

You can specify custom color for all three log levels (info, warn and error).

const logger = new Logger<"prod", "dev">({
  // ... default options
  styles: {
    colors: {
      info: Logger.colorizer.bold().font().rgb(100, 100, 255),
      error: Logger.colorizer.bold().font().rgb(255, 100, 100),
      warn: Logger.colorizer.bold().font().rgb(200, 200, 100)
    }
  }
})

Custom prefix format

You can specify custom time format for all three log levels (info, warn and error). The libarary support 4 format vars, hh (hour), mm (minutes), ss (seconds) and lvl (log level).

const logger = new Logger<"prod", "dev">({
  // ... default options
  styles: {
    format: "lvl hh::mm::ss"
  }
})

logger.console.info("Test the custom time format.")

This will log follow message.

  INFO 12::54::56 Test the custom time format.