a smartlog destination targeting the local console
Go to file
2017-01-21 19:52:34 +01:00
dist update colors 2017-01-21 19:52:31 +01:00
docs add coverage 2016-09-02 17:26:55 +02:00
test improve figlet coloring 2017-01-21 19:04:40 +01:00
ts update colors 2017-01-21 19:52:31 +01:00
.gitignore integrate npmpage 2016-09-02 12:50:07 +02:00
.gitlab-ci.yml fix gitlab yml 2016-09-02 12:57:33 +02:00
.npmignore integrate npmpage 2016-09-02 12:50:07 +02:00
LICENSE Initial commit 2015-09-20 17:42:50 +02:00
npmts.json update smartenv dependency 2016-02-20 10:29:35 +01:00
package.json 6.0.5 2017-01-21 19:52:34 +01:00
README.md update to version 2 2016-10-16 02:26:43 +02:00
tslint.json update to version 2 2016-10-16 02:26:43 +02:00

beautylog

beautiful logging, TypeScript ready

Availabililty

npm git git docs docs

Status for master

build status coverage report Dependency Status bitHound Dependencies bitHound Code TypeScript node

Usage

import * as beautylog from 'beautylog'

beautylog.log('some log message') // normal console log message
beautylog.info('some log message') // info console log message
beautylog.ok('some log message') // ok console log message
beautylog.warn('some log message') // warn console log message
beautylog.success('some success message') // success console log message
beautylog.error('some error message') // error console log message

The plugin produces beautiful output like this: console.png

Ora Integration

beautylog wraps the excellent ora module from npm to better work with beautylog. In general that means that you can log persistent messages WHILE you are actually having an active Ora object. beautylog handles all the fuss for you.

let myOra = new beautylog.Ora('my awesome text', 'blue')
myOra.start()
beautylog.info('some persistent text') //does not disturb myOra
console.log('something') // even this works because console.log is monkeypatched by beautylog
myOra.text('some updated text')
myOra.stop()

Centralized remote logging

Beautylog makes it easy to have all your node applications log to a remote location.

Currently supported remote providers:

  • loggly.com
beautylog.remote.loggly({
    token: 'loggly-token',
    subdomain: 'loggly-subdomain',
    appName: 'some App Name',
    serverName: 'some Server Name'
})

Note: since beautylog monkeypatches all console log methods. There is no need to change anything in your code. Everything that is getting logged to your console by node will get logged to loggly as well.

For more information read the docs!

npm