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

nv-log-gray

v1.0.5

Published

nv3-cli utility files

Readme

Install

npm i -D nv-log

⚠️ We do not recommend installing this module globally

Usage

// default name nv3
const logger = require('nv-log').logger;
logger.info('Server Starting');
import {logger, loggerColors, loggerSymbols} from 'nv-log'
logger.info('Server Starting');
loggerColors.green('message')
loggerSymbols.debug

ℹ️ The logger returned is unique by default, due to the nature of the nv ecosystem. Please reference the unique option below for disabling this feature and to force caching

Options

| Name | Type | Default | Description | | :---------------------------: | :---------: | :------------: | :---------------------- | | name | {String} | ''<unknown>' | Log Name (Required) | | level | {String} | 'info' | Log Level | | unique | {Boolean} | true | Log Uniqueness | | timestamp | {Boolean} | false | Log Timestamps |

name

Specifies the name of the log to create. This option is required, and used to differentiate between loggers when nv-log is used in multiple projects executing in the same process

const logger = log({ name: 'wds' });

level

Specifies the level the logger should use. A logger will not produce output for any log level beneath the specified level. Available levels and order are:

['info', 'warn', 'error', 'trace', 'debug', 'silent'];
const logger = log({ level: 'error' });

logger.error(err);

ℹ️ The level names shown above correspond to the available logging methods, with the notable exception of the silent level

unique

If false, instructs the logger to used cached versions of a log with the same name. Due to the nature of the nv ecosystem and multiple plugin/loader usage in the same process, loggers are created as unique instances by default. By passing false for this property, the module is instructed to cache the requested logger

const logger = log({ unique: true });

timestamp

If true, instructs the logger to display a timestamp for log output, preceding all other data

const logger = log({ timestamp: true });