The Hackable Log
Last updated 2 months ago by kikobeats .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install acho 
SYNC missed versions from official npm registry.


Last version Build Status Coverage Status Dependency status Dev Dependencies Status NPM Status Donate

The <hackeable /> Log


  • Different log levels skins.
  • Beauty object interpolation.
  • Diff & log trace support.
  • Easy to customize, easy to hack.


npm install acho


Logging levels

<summary> Examples </summary>


The first thing you need to do is create a new log instance:

const acho = require('acho')
const log = acho()

Then you can print a log based on the level:

const acho = require('acho')
const log = acho()'hello world')

All methods are chainables:

const acho = require('acho')
const log = acho()

  .info('hello world')
  .error('something bad happens')

Establishing the loglevel is a good way to filter out undesired information from output. The available levels by default are:

  • fatal : Display calls to .fatal() messages.
  • error : Display calls to .fatal(), .error() messages.
  • warn : Display calls from .fatal(), .error(), .warn() messages.
  • info : Display calls from .fatal(), .error(), .warn(), info() messages.
  • debug : Display calls from .fatal(), .error(), .warn(), info(), debug() messages.

Additionally exists two special levels:

  • muted : Avoid all output.
  • all : Allow print all message types.

The default log level is all. You can define it in the constructor:

const acho = require('acho')
const log = acho({ level: 'debug' })

or at runtime:

log.level = 'debug'

Internal Store

Sometimes, when you are interacting with a logger you need to store the logs to be used later instead of print all of them.

We define .push as accumulator for store the log internally:


const acho = require('acho')
const log = acho()

log.push('success', 'good job', 'well done', 'great!')

If you want to print previously stored messages, just call the method .print:


or you can retrieve the logs programatically from the internal storage at acho.messages

The method .add combine .push and .print actions in one: It store the message internally but also print the log.


log.add('info', 'this message is printed and stored')


<summary> Examples </summary>


We use printf-style formatting. Below are the officially supported formatters:

Formatter Representation
%s String.
%d Number (both integer and float).
%j JSON serialization in one line
%J JSON pretty object in multiple lines
%% Single percent sign ('%'). This does not consume an argument.

By default, the %j is applied when you pass an object to be logged:

const acho = require('acho')
const log = acho(){ hello: 'world', foo: 'bar' })
// => 'info hello=world foo=bar'

If you want to use a different formatter, use printf markup:

const acho = require('acho')
const log = acho()'formatting with object interpolation %J', {
  hello: 'world',
  foo: 'bar',
  deep: {
    foo: 'bar',
    arr: [1, 2, 3, 4, 5]


<summary> Examples </summary>

One of the acho compromise is be easy to adapt. You can completely customize all the library functionalities.

For example, suppose you want to add a timestamp before your logs:


const acho = require('acho')

const log = acho({
  // Customize how to print the 'type' of each message
  outputType: type => `[${type}]`,

  // Customize how to print the message.
  // Add things before and/or after.
  outputMessage: message => `${} :: ${message}`
})'I am hungry')

That's all.



It creates a logger instance.



Type: string
Default: loglevel

Instead of print the type log level, print the keyword. By default this behavior is not activated.

You can pass the special keyword symbol to show an unicode icon. This is special behavior for CLI programs.


Type: string
Default: ' '

It adds an alignment separator between the type of the message and the message.

You can provide your own separator or disable it providing a false.


Type: boolean
Default: false

Prints trace between log from the same level. Specially useful to debug timings.


Type: boolean
Default: false.

Enable or disable print log level in upper case.


Type: boolean|number
Default: false.

Prints a numeric counter trace associated with each log line.

The value provided is the minimum quantity of time in milliseconds to consider print a different counter.


Type: number
Default: 2.

The amount of left whitespace between the property key and all of it's sub-properties.

This option is only applied under JSON pretty object in multiple lines (%J).


Type: number
Default: Infinity.

Colapses all properties deeper than specified by depth.

This option is only applied under JSON pretty object in multiple lines (%J).


Type: string
Default: all

Provides the logging level. This sets from what level print logs using tranport.

Additionally you can provide muted to express don't print logs.


Type: function
Default: console.log

Defines where write the log message.


Type: object

You can provide the types and priorities.


Type: object

It provides a initial internal store state per each log level. This option is useful when you want to integrate the logger with the ouptut of a delayed function.


Type: function

Provides a function that determines how to print the messages. By default uses .generateMessage for generate the mesage that will be outputted.


Type: function

Provides a function to customize the type in the output.


Type: function

Provides a function to customize the message in the output.


Type: function

Provides a function that generate the message to be outputted. It combines other internal methods for generate the output (as .isPrintable or .colorize) and normally you are not interested in the definition of it, but you can provide it as option as well.


Type: function

Provides a function used to generate the type message.

.push(<type>, <message>)

Store a message of given type internally.


Type: string


Type: string

.add(<type>, <message>)

Store a message of given type internally and also output it.


Type: string


Type: string

For each level you have a function following the pattern:


Prints all messages internally stored.


For each log level that you declared in the constructor (or the default log levels provides by the library if you don't declare nothing) will be created a function with the same name to output a message with these log level.


Type: string


acho © Kiko Beats, Released under the MIT License.
Authored and maintained by Kiko Beats with help from contributors. · GitHub Kiko Beats · Twitter @kikobeats

Current Tags

  • 4.0.6                                ...           latest (2 months ago)

46 Versions

  • 4.0.6                                ...           2 months ago
  • 4.0.5                                ...           4 months ago
  • 4.0.4                                ...           2 years ago
  • 4.0.3                                ...           2 years ago
  • 4.0.2                                ...           2 years ago
  • 4.0.1                                ...           2 years ago
  • 4.0.0                                ...           3 years ago
  • 3.3.2                                ...           3 years ago
  • 3.3.1                                ...           3 years ago
  • 3.3.0                                ...           3 years ago
  • 3.2.1                                ...           3 years ago
  • 3.2.0                                ...           3 years ago
  • 3.1.2                                ...           3 years ago
  • 3.1.1                                ...           4 years ago
  • 3.1.0                                ...           4 years ago
  • 3.0.2                                ...           4 years ago
  • 3.0.1                                ...           4 years ago
  • 3.0.0                                ...           4 years ago
  • 2.8.0                                ...           4 years ago
  • 2.7.2                                ...           4 years ago
  • 2.7.1                                ...           4 years ago
  • 2.7.0                                ...           4 years ago
  • 2.6.2                                ...           4 years ago
  • 2.6.1                                ...           4 years ago
  • 2.6.0                                ...           4 years ago
  • 2.5.3                                ...           4 years ago
  • 2.5.1                                ...           4 years ago
  • 2.5.0                                ...           4 years ago
  • 2.4.2                                ...           4 years ago
  • 2.4.1                                ...           4 years ago
  • 2.4.0                                ...           5 years ago
  • 2.3.0                                ...           5 years ago
  • 2.2.1                                ...           5 years ago
  • 2.1.0                                ...           5 years ago
  • 2.0.0                                ...           5 years ago
  • 1.0.8                                ...           5 years ago
  • 1.0.7                                ...           5 years ago
  • 1.0.66                                ...           5 years ago
  • 1.0.6                                ...           5 years ago
  • 1.0.5                                ...           5 years ago
  • 1.0.4                                ...           5 years ago
  • 1.0.3                                ...           5 years ago
  • 1.0.2                                ...           5 years ago
  • 1.0.1                                ...           5 years ago
  • 1.0.0                                ...           5 years ago
  • 0.1.0                                ...           5 years ago
Maintainers (1)
Today 0
This Week 3
This Month 147
Last Day 0
Last Week 48
Last Month 290
Dependencies (4)
Dev Dependencies (11)

Copyright 2014 - 2016 © |