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

terminal-logger

v0.2.3

Published

It's a console logger inherited from abstract-logger.

Downloads

5,520

Readme

terminal-logger npm

Build Status Code Climate Test Coverage downloads license

Terminal-logger prints the message to the console.

All logs are done against STDERR, letting you stdout for meaningfull value and redirection, should you need to generate output this way.

  • Customize colorful status
  • Single-line update
  • table supports

Usage

logger  = require('terminal-logger')('test')
//change the logging level.
logger.level = 'info'

logger
  .write()
  .status.info('Doing something')
  .status('info','Doing something same')
  .status.force('Forcing filepath %s', 'some path')
  .status.conflict('on %s', 'model.js')
  .status.ok('good')
  .status.error('sth error')
  .status.create(logger.table([['a:', 213], ['b:', 111]]))
  .write()
  .tick('<-This is ok')
  .cross('<-this is a wrong cross flag')

logger.log({
  message: '${name} - ${status}: Hi here ${title}'
  , title: 'Today Title'
  , status: 'ok'
})

the result:

result

Single-line update:

log = require('terminal-logger/lib/single-line')('test')
log.level = 'info'
dash = '>'
singleLineLog = ->
   dash = dash.replace('>', '->')
   log.status("info", "update:", dash)
   dash = '>' if dash.length > 60
   setTimeout(singleLineLog, 500)
singleLineLog()

the result:

single-line-result

API

TODO

Changes

v0.2.0

  • add the emergency/alert/critical/error/warning/notice/info/debug/trace(message[, context], args...) methods:
    • these are same as logger.status[xxx]. (v0.2.3)
  • add the logging level supports
  • broken: remove the predefined status as its logging method utility
  • add status(aStatus, aMessage, ...) and status[status](aMessage,...) methods
  • add customizable colors and statusLevels
    • the default colors(map the status or level to color):
      • skip: 'magenta'
      • force: 'yellow'
      • create: 'green'
      • invoke: 'bold'
      • conflict: 'red'
      • identical: 'cyan'
      • ok: 'green'
      • emergency: ['red', 'bold']
      • alert: 'red'
      • critical: 'red'
      • error: 'red'
      • warning: 'yellow'
      • notice: 'gray'
      • info: 'gray'
      • debug: 'blue'
      • trace: 'blue'
      • '✔': 'green'
      • '✗': 'red'
      • name: 'blue' # it's NOT the status, it's just the logger name's color.
    • the default statusLevels(map the status to logging level):
      • skip: 'warning'
      • force: 'warning'
      • create: 'notice'
      • invoke: 'notice'
      • conflict: 'error'
      • identical: 'error'
      • ok: 'notice'
      • '✔': 'notice'
      • '✗': 'error'

License

MIT