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

@frasermcc/log

v2.6.2

Published

Simple logging utility

Readme

@frasermcc/log

A super simple log.

npm version

npm i @frasermcc/log

Usage


import Log, { Level } from "@frasermcc/log";

// Set log level to trace
Log.level(Level.TRACE);

// White text.
Log.trace("Hello World");

// Green text.
Log.info("Hello World");

// Yellow text.
Log.warn("Hello World");

// Red text.
// Will print a stack trace.
Log.error("Hello World");

// White text on red background.
// Will print a stack trace.
// Will exit the application.
Log.critical("Hello World");

General output format is as follows:

[1:37:58 AM]  [INFO]      Hello World
[1:37:58 AM]  [WARN]      Hello World
[1:37:58 AM]  [ERROR]     Hello World
    at Function.Log.error (D:\Projects\f-log\src\index.ts:72:27)
    etc...

Other Utilities

Trace

The @Trace decorator can be used on class methods as follows:

class Test {
  @Trace()
  public test(a: any, b: any) {
    return "hello!";
  }
}

new Test().test(5, { a: 5 });

with the output:

[2:04:35 AM]  [TRACE]     [Test] test(args) => result in 0.0130ms.
  Arguments: [ 5, { a: 5 } ]
  Returns: hello!

Note that the log level of the @Trace decorator is set to TRACE by default. It can be changed by passing a Level to the decorator:

@Trace(Level.INFO)

Persist

Logs can be persisted to a file.

// save logs to file named myLog.log
Log.persist("myLog.log");

// default name is the Log level with the log file extension.
// save logs to file named WARN.log
Log.level(Level.WARN)
Log.persist()

Block

The Log#block(message, color) method can be used to print a block of text.

import Log, { chalk } from ".";

Log.block("Hello", chalk.blue);

with the output:

  _   _      _ _
 | | | | ___| | | ___
 | |_| |/ _ \ | |/ _ \
 |  _  |  __/ | | (_) |
 |_| |_|\___|_|_|\___/