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 🙏

© 2025 – Pkg Stats / Ryan Hefner

logzly

v1.0.1

Published

A lightweight logging utility

Downloads

103

Readme

Logzly

A simple logger.

Getting Started

Install it:

yarn add logzly
# or
npm i logzly

Then import it where you want to use it.

import { log } from "logzly";

Log Types

The logger has several types with escalating log levels. Each log command requires a topic and optionally takes an object of data as the second argument.

log.trace("Topic.Name", {});
log.debug("Topic.Name", {});
log.info("Topic.Name", {});
log.warn("Topic.Name", {});
log.error("Topic.Name", {});
log.fatal("Topic.Name", {});

Log Levels

The log levels are:

  • trace
  • debug
  • info
  • warn
  • error
  • fatal

If you set your log level at a level above the log type you are logging, it will not be logged:

log.setLogLevel("debug");
log.trace("Trace.Topic"); // Never logs
log.debug("Debug.Topic"); // Logs
log.info("Info.Topic"); // Logs

You can also set the log level by setting the LOG_LEVEL environment variable, but setLogLevel will override it if used.

Filtering

You may set a filter and exclude all logs that do not match the filter.

log.setFilter("Foo.*");
log.info("Bar.Baz"); // Never logs
log.info("Foo.Baz"); // Logs

By default, the filter is set to * which allows all logs. You can also set this using the LOG_FILTER environment variable but setFilter will override it if used.

Metadata

You can set any arbitrary meta data with log.addMetaData()

log.addMetaData({
  foo: "bar",
});

log.trace("Foo.Bar"); // "Foo.Bar" { _meta: { foo: "bar" } }

The log.addMetaData() will extend any previous metadata. log.clearMetaData() will reset the meta object to empty.