a smartlog destination targeting the local console
dist | ||
docs | ||
test | ||
ts | ||
.gitignore | ||
.gitlab-ci.yml | ||
.npmignore | ||
LICENSE | ||
npmts.json | ||
package.json | ||
qenv.yml | ||
README.md | ||
tslint.json |
beautylog
beautiful logging, TypeScript ready
Availabililty
Status for master
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
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.
beautylog.ora.start('Hi, this is some text!', 'blue')
beautylog.info('some persistent text') //does not disturb ora
console.log('something') // even this works because console.log is monkeypatched by beautylog
beautylog.ora.text('some updated text') // switches the text
beautylog.ora.stop()
Centralized remote logging
Beautylog makes it easy to have all your node applications log to a remote location.
import { Loggly } from 'beautyremote'
let myLogglyRemote = new Loggly({
token: 'my_super_long_token_here'
})
beautylog.registerRemote(myLogglyRemote)
Note: 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 a remote as well.
For more information read the docs!