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

logerian

v3.1.0

Published

Logerian is a quick and dirty logging utility.

Downloads

40

Readme

Description

Logerian is a logging utility made by me! I made this logging utility mainly because I am too dumb to understand other loggers like winston and signale. If you're willing to contribute, please read CONTRIBUTING.md.

Demo

GIF of library in action

Usage

To use this logger, you can simply just create a new logger instance and it'll work. It uses default options, which is the built-in coloredLog prefix, routing log levels correctly to stdout and stderr respectively:

import { Logger } from "logerian"; // ES import
const { Logger } = require("logerian"); // CJS import

const logger = new Logger();

logger.info("Hello World!");
// Output: [17:43:01] [INFO] Hello World!

By default, the logger adds a prefix with a timestamp and log level as shown in the example code above. If you wish to change that, you'll have to define a stream when you create the logger.

const logger = new Logger({
  streams: [
    {
      stream: process.stdout,
    },
  ],
});

logger.info("foobar");
// Output: foobar

A logger can utilize multiple output streams:

const logger = new Logger({
  streams: [
    {
      stream: process.stdout,
    },
    {
      stream: fs.createWriteStream("log.txt"),
    },
  ],
});

logger.info("Iron Man dies in Endgame");
// Output: Iron Man dies in Endgame
logger.info("Steve Rogers is old!!");
// Output: Steve Rogers is old!!
# log.txt
Iron Man dies in Endgame
Steve Rogers is old!!

There's also a neat thing called log levels!

import { Logger, LoggerLevel } from "logerian";
const { Logger, LoggerLevel } = require("logerian");

const logger = new Logger({
  streams: [
    {
      level: LoggerLevel.WARN,
      stream: process.stdout,
    },
    {
      level: LoggerLevel.DEBUG, // Debug level is default
      stream: fs.createWriteStream("log.txt"),
    }
  ],
});

// Logs to both - stdout and log.txt
logger.error("Uh oh! There's an error!");

// Logs only to log.txt
logger.debug("By the way, there's an error because your code sucks!");

If you want to use pinned lines (as they're called in code), just use logger.createPinnedLine. The rest should be pretty easy to understand from the documentation

For advanced users, view the JSDocs.