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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@dot/log

v0.1.5

Published

A beautiful and minimal logger for all applications

Downloads

81,435

Readme

@dot/log

A beautiful and minimal logger for all applications

Requirements

This package requires an Active LTS Node version (v18+).

Install

Using npm:

npm install @dot/log --save

Usage

Create a new logger and use it to log something wild:

import { log } from '@dot/log';

log.info('Jingle Bells, Batman Smells');
log.warn('Robin laid an egg');
log.error('The Batmobile lost a wheel');
log.debug('And the Joker got away');

And there will appear magic in your console

To name the log pass the name in the getLog options:

const log = getLog({ name: 'batman' });

When logging an object the nesting can be only one level deep. If the nesting level of the object exceeds one level then a RangeError exception will be thrown.

Setting the Log Level

By default, each log instance is set to the 'info' level. The log level can be set one of two ways:

  1. By direct manipulation of the log itself, which can be useful for one-off log instances:
import { log } from '@dot/log';

log.level = 'debug'; // change from the default 'info' level
  1. Using an the DOT_LOG_LEVEL environment variable:
DOT_LOG_LEVEL=debug

Meta

CONTRIBUTING

LICENSE (Mozilla Public License)