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

@nlf/cli-logger

v1.1.0

Published

a logger that i use for cli tools

Readme

cli-logger

This is a small logger that I wrote for usage in my own cli tools. It's pretty much meant to fit my needs and that's it. If it's useful for you too, awesome.

API

new Logger({ name, level, format })

Create a new logger instance. The options are as follows:

  • name: if provided, this will log as part of each entry made by this logger instance. This is mostly useful if you have multiple sources of logs in your app and want them to be distinguished from each other.
  • level: the minimum level that log entries must match before they're actually printed. the default is 'info' and may be set to one of 'debug', 'info', 'warn', or 'error'
  • format: the format to print the timestamp in, this is passed directly to dateformat and defaults to 'HH:MM:ss.l'.
  • hrtime: measure timers using process.hrtime() (or process.hrtime.bigint() if available) and print more detailed time strings, defaults to false

logger.debug(), logger.info(), logger.warn(), logger.error()

Log an entry with the given level. Arguments are passed directly to util.format and prepended with a timestamp, the level as a string, and if provided your logger's name.

logger.count(id, level)

Log a count of an entry. Any log line that is given the same id will increment the count and print both the id and the number of times that id (at the same level) has been called. The level parameter is optional and defaults to 'info'.

logger.time(id, level)

Start a timer with the given id (level is optional, and defaults to 'debug'). A log entry will be printed at the given level with a message informing the user the timer has started.

logger.timeEnd(id, level)

End the timer with the given id (level is optional, and defaults to 'info'). A log entry will be printed at the given level with a message informing the user the timer has finished, as well as how much time elapsed since the timer started. Note that unlike logger.count(), the level here does not need to match the level given to logger.time().