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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@exortions/logger

v1.1.3

Published

An advanced, completely configurable Logger for JS & TS.

Readme

Logger

An advanced, completely configurable Logger for JS & TS.

Installation

npm install --save @exortions/logger
yarn add @exortions/logger

Usage

import LoggerFactory from '@exortions/logger';

// Package for using colors
import colors from 'colors';

// initialize the factory

const factory = new LoggerFactory();

// create a logger
const logger = factory.createLogger(
    'my-logger',
    // Formatting
    {
        debug: colors.bold(colors.cyan('[$[caller]] $[message]')),
        info: colors.bold(colors.blue('[$[caller]] $[message]')),
        warn: colors.bold(colors.yellow('[$[caller]] $[message]')),
        error: colors.bold(colors.red('[$[caller]] $[message] $[err]'))
    },
    // File logging options
    {
        levelsToWrite: ['debug', 'info', 'warn', 'error'], // or '*' or 'all' or 'none',
        write: true, // if false, no logs will be written to file.
        file: path.join(__dirname, '../logs/' + new Date().toISOString() + '.log')
    },
    // Caller name replacements
    {
        Index: 'Main' // first is always uppercase, so not index, but Index, even if the filename is 'index.js'.
    },
    // Requirements for a log:
    {
        debug: true, // could be something like process.env.DEBUG === 'true'
        info: true,
        warn: true,
        error: true
    }
)

logger.debug('This is a debug message');
logger.info('This is an info message');
logger.warn('This is a warn message');
logger.error('This is an error message');
logger.error('This is an error message with an error', new Error('This is an error'));

// example of using the Logger type
function getMyLogger(): Logger | undefined {
    return factory.getLogger('my-logger');
}

// make sure the logger is actually created
const myLogger = getMyLogger();

if (!myLogger) throw new Error('Logger not found');

console.log(myLogger === logger); // true

All placeholders are contained inside the $[] brackets.

Placeholders:

message
month
day
year
hour
minute
second
ms
caller - the name of the caller file, for example: index.js -> Index
err - the error, if any or empty string
pid
ppid
time
timezone
uptime
memory
memory-rss
memory-heap-total
memory-heap-used
memory-external
memory-b
memory-kb
memory-mb
memory-gb