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

kittie

v4.2.0

Published

A fast, simple logger with children

Downloads

16

Readme

kittie

Build Status

A fast, simple logger with children

Install

$ npm install [--save] kittie

API

log

A logger is exported. To use:

const log = require('kittie')
log.silly('hello')
log.verbose('hello')
log.info('hello')
log.http('hello')
log.warn('hello')
log.error('hello')

// to change the log level
log.level = 'silly'

// we also support child loggers
const debug = log.child('debug')
debug.level = process.env.DEBUG
  ? 'silent'
  : 'silly'

debug.info('Hey! This is a debug message')

Each logger has the following methods:

silly(message[, meta])

Will only be logged if the logger's level is set to silly.

verbose(message[, meta])

Will only be logged if the logger's level is set to silly or verbose.

info(message[, meta])

Will only be logged if the logger's level is set to silly, verbose, or info.

http(message[, meta])

Will only be logged if the logger's level is set to silly, verbose, info, or http.

warn(message[, meta])

Will be logged unless the logger's level is set to silent or error.

error(message[, meta])

Will be logged unless the logger's level is set to silent.

inspect(obj[, depth])

log.inspect() is a bit different than the other log methods. It functions at the verbose log level, but calls util.inspect() under the hood.

child(component)

Creates a new child logger that inherits settings from it's parent. A child logger can be used to distinguish different modules inside a single project.

Examples

Check out the examples/ directory to see some examples

Log levels

  • silly
  • verbose
  • info (Default)
  • http
  • warn
  • error
  • silent

Test

$ npm test

TODO

  • Add better documentation

Author

Evan Lucas

License

MIT (See LICENSE for more info)