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

logforth

v1.2.2

Published

Simple logging framework for NodeJS

Downloads

119

Readme

Logforth

Release

This is a simple logging framework specifically build for NodeJS.

I have been using several logging frameworks in the past, but I had always issues with one or another quirks of each. After comparing how each of them works, as well as looking for more inspiration in the Rust logging frameworks I came up with the design for this logging library.

Logforth supports both pretty printing for development and ndjson output for production. Each log entry has a mandatory message and optional attributes. Attributes are included as-is in ndjson output and pretty printed in development.

Installation

npm

npm i logforth

pnpm

pnpm add logforth

Usage

First you want to instantiate a new instance of the logger:

import {Logger} from "logforth";

const logger = new Logger();
logger.info("First logger test");

Min log level

By default, Logforth will log all events. You can limit this through the minLevel option:

import {Logger, LogLevel} from "logforth";

const logger = new Logger({ minLevel: LogLevel.Info });

In order to disable logging completely you can pass disableLogging to minLevel:

import {Logger, disableLogging} from "logforth";

const logger = new Logger({ minLevel: disableLogging });

Pretty printing

In development, you might prefer to see pretty printed log message. A simple switch between production and development could look like this:

import {Logger, NdJsonTransport, PrettyTransport} from "logforth";

const logger = new Logger({
    transport: process.env.NODE_ENV === "production"
        ? new NdJsonTransport()
        : new PrettyTransport()
});

Attributes

You can pass arbitrary attributes to each log entry:

logger.info("I contain attributes", { foo: "bar" });

In ndjson output they will be inlined with the rest of the log entry. Thus, you must not use the following attribute names: time, level and msg.

Default attributes

If you want to have specific attributes always present, e.g. the hostname of the running process, you can include this in the constructor:

const logger = new Logger({ attributes: { "hostname": "foo" } });

Context aware logging

Logforth supports logging in context aware situation, for instance when you want to keep track of a request ID. You can do so through the withContext() method. The following example demonstrates how to do this in Koa:

koaApp.use((context, next) => {
    return logger.withContext({ requestId: "foo" }, next);
});