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

@satisfact-api/logger

v1.0.0

Published

Simple and easy to use text logger.

Downloads

2

Readme

Satisfact-api / Logger

Test and lint

Simple and easy to use text logger.

Usage

The logger must be initialized then can be called with one of the four log levels:

  • trace
  • info
  • warn
  • error
import Logger from 'project-logger';

const logger = Logger('context');

logger.warn('Here comes an object');
logger.warn({
  hello: 'World',
});

Output:

Output

Reference

The Logger module exports a factory function that is used to generate loggers instances.

Factory

Logger([context], [options])

Logger([options])

The factory generates logger instances, it can be initialized with a context and with options.

If no context is provided, the logger will take the current file location as context.

Examples:

import Logger from 'logger';

// Simple initialization with a context
const simple = Logger('my-context');

// No context provided, the file location will be used
const noContext = Logger();

// The logger instance can be initialized with some options
const withOptions = Logger('my-context', {
  trim: false,
});

Options

The options attribute is an object that can contains :

  • colors (object): Object defining the colors used for each kind of log levels: trace, info, warn, error. Each attribute of the color option must be a function that will receive an input and returns it colorized. Internally, chalk do the default colorization. If null, colorization is disabled.
  • dateFormat (string): Date format used to display the dates. The formater being [dayjs][days], the format must follow their own format described here. If null or empty, no date will be displayed.
  • trim (boolean): Option to toggle the trim of each strings to log. It does not affect objects and errors.
  • ignoreEmpty (boolean): Option to toggle the empty lines removal.
  • output (function): Output method called for each line to display. Defaults to process.stdout.write.
  • logLevel (string): Minimum log level to diplay. Can be either TRACE, INFO, WARN or ERROR. Defaults to process.env.LOG_LEVEL or WARN if it does not exists.

configure

configure(options)

The module also export a method overriding the global configuration of all the Logger instances. It takes the same arguments as the Factory options.

Instance

Each instance consist of 4 methods: trace, info, warn, error:

logger.trace(content)

logger.info(content)

logger.warn(content)

logger.error(content)

The attribute content can be a string, object or error. The log only outputs if the configured log level is equal or "inferior" of the log method.

Get the current log level

getLogLevel()

You can retrieve the current log level with the method getLogLevel. It can be useful if you need to conditionnaly start heavy log loops on your processes.