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

@littlethings/log

v3.0.9

Published

A simple logging utility.

Downloads

50

Readme

LittleLog

A simple logging utility.

Preview

Installation

Install using your favorite package manager:

npm install @littlethings/log

Usage

Configuration

Programmatic

To configure LittleLog using the configure function, see the following example.#

import { configure, LogLevel } from "littlelog";

configure({
	/**
	 * How verbose the logging should be.
	 * Defaults to `process.env.LOG_LEVEL`.
	 */
	level: LogLevel.Info,
	/**
	 * An optional filter used to filter logs based on prefix.
	 * Defaults to `undefined`.
	 */
	filter: "my-prefix",
	/**
	 * Whether or not to log prefixes before messages.
	 * Defaults to `true`.
	 */
	prefix: false,
	/**
	 * Whether or not to log timestamps.
	 * Defaults to `true`.
	 */
	timestamp: false,
	/**
	 * Whether or not to enable color logging.
	 * Defaults to `true` if in a TTY, otherwise defaults to `false`.
	 */
	color: false,
	/**
	 * Whether or not to enable icons in logs.
	 * Defaults to `false`.
	 */
	icons: true,
});

Environment Variables

Default values can be supplied via the environment, but they may be overriden by programmatic configuration as seen above.

# Set the log level (options are: SILENT, INFO, DEBUG, TRACE).
LOG_LEVEL=INFO

# Don't log prefixes.
LOG_PREFIX=false

# Enable timestamps.
LOG_TIMESTAMP=true

# Filter logs based on prefix regex.
LOG_FILTER="^my-app$"
# You can use the more common `DEBUG` variable for filtering if you prefer.
#DEBUG="^my-app$"

# Enable color.
LOG_COLOR=true

# Disable color.
LOG_COLOR=false

# Or, for compatibility with Chalk, you can use `FORCE_COLOR`.
FORCE_COLOR=1
FORCE_COLOR=0

# Enable icons.
LOG_ICONS=true

Logging

To log messages using the base logger, see the following example.

import log from "littlelog";

log.info("This is an info log.");

log.debug("This is a debug log.");

log.trace("This is a trace log.");

log.warn("This is a warn log.");

log.error("This is an error log.");

log.fatal("This is a fatal log.");

To create a child logger with a unique prefix, see the following example.

import littlelog from "littlelog";

// This will have the prefix `MyLogger`.
const myLogger = littlelog.child("MyLogger");

myLogger.info("This is an info log.");

myLogger.debug("This is a debug log.");

myLogger.trace("This is a trace log.");

myLogger.warn("This is a warn log.");

myLogger.error("This is an error log.");

myLogger.fatal("This is a fatal log.");

// You can continue to create child loggers if you want!
// This will have the prefix `MyLogger:MySubLogger`.
const mySubLogger = littlelog.child("MySubLogger");

mySubLogger.info("This is an info log.");

mySubLogger.debug("This is a debug log.");

mySubLogger.trace("This is a trace log.");

mySubLogger.warn("This is a warn log.");

mySubLogger.error("This is an error log.");

mySubLogger.fatal("This is a fatal log.");