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 🙏

© 2025 – Pkg Stats / Ryan Hefner

rauricoste-logger

v2.2.6

Published

This is a lightweight library to handle logs in an application. It is written in Typescript but can be used in a JS project.

Readme

Summary

This is a lightweight library to handle logs in an application. It is written in Typescript but can be used in a JS project.

Usage

Simple usage:

import { logger } from "rauricoste-logger";

logger.info("hello world");
// 2025/10/17 11:31:31.508 INFO _ hello world

Log levels

Default log level is INFO

import { logger } from "rauricoste-logger";

logger.debug("hello world");
// not working
logger.info("hello world");
// 2025/10/17 11:31:31.508 INFO _ hello world

There are 5 default log levels:

import { logger, LoggerLevel } from "rauricoste-logger";

logger.setLevel(LoggerLevel.DEBUG);

logger.debug("hello world");
logger.info("hello world");
logger.warn("hello world");
logger.error("hello world");
logger.fatal("hello world");
// 2025/10/17 11:31:31.507 DEBUG _ hello world
// 2025/10/17 11:31:31.508 INFO _ hello world
// 2025/10/17 11:31:31.508 WARN _ hello world
// 2025/10/17 11:31:31.508 ERROR _ hello world
// 2025/10/17 11:31:31.508 FATAL _ hello world

It is possible to log at a custom log level:

logger.log(23, "special log level");
// 11:24:56.431 WARN _ special log level

Log level are actually mapped to a number:

const LoggerLevel = {
  DEBUG: 10,
  INFO: 20,
  WARN: 30,
  ERROR: 40,
  FATAL: 50,
};

The log level of a logger can be set dynamically:

import { logger, LoggerLevel } from "rauricoste-logger";

logger.setLevel(LoggerLevel.DEBUG);
logger.debug("hello world");
// nothing is logged

logger.setLevel(LoggerLevel.WARN);
logger.debug("hello world");
// 2025/10/17 11:36:58.671 DEBUG _ hello world

Logger hierarchy

Loggers can have children that inherit the log levels and appenders.

import { logger, LoggerLevel } from "rauricoste-logger";

const childLogger = logger.getLogger("child");
childLogger.warn("test");
// 2025/10/17 11:42:46.365 WARN _.child test

logger.setLevel(LoggerLevel.WARN);
console.log(logger.level);
// 30
console.log(childLogger.level);
// 30

logger.setLevel(LoggerLevel.ERROR);
console.log(logger.level);
// 40
console.log(childLogger.level);
// 40

Child loggers are linked to their name:

import { logger } from "rauricoste-logger";

const childLogger = logger.getLogger("child");
const childLogger2 = logger.getLogger("child");
console.log(childLogger === childLogger2);
// true

Appenders

By default, the console appender is configured but it is possible to remove or add any appender.

An appender is defined by:

type Appender = (logger: Logger, level: LoggerLevel, ...args: any[]) => void;

You can change the appenders:

import { type Appender, Logger, logger, LoggerLevel } from "rauricoste-logger";

const dumbAppender: Appender = (
  logger: Logger,
  level: LoggerLevel,
  ...args
) => {
  console.log(logger.name, level, ...args);
};
logger.appenders = [dumbAppender];

logger.info("hello world");
// _ 20 hello world