Add different and extendable logging transports

It would be nice if Logdown could write to log files.

The atma-logger for example is able to write to the filesystem or to a remote server (via HTTP): https://github.com/atmajs/atma-logger#transports

There is also winston, a multi-transport async logging library. With winston logging transports can be changed the following way:

winston = require('winston');

winston.add(winston.transports.File, {
  filename: config.logging_file,
  handleExceptions: true,
})
.remove(winston.transports.Console)
.info('Name', 'Message');

Would be great to have something similar with Logdown. 😃

[caiogondim]

I like the idea a lot.

I would make as simple as possible, using an array that is a collection of functions that will be called on every logdown method.

logdown.transports = []

My proposal for the API:

• Adding transport

logdown.transports = logdown.transports.concat([
  (msg) => {
    console.log(msg)
  },
  (msg) => {
    fs.writeFile(filePath, msg)
  }
])

• Removing transport

logdown.transports.splice(1, 1)

• List transports

logdown.transports // => Array of functions

Don’t think we should provide any custom transport function, since they are super easy to implement.

[caiogondim]

BTW. Would it better to add Babel? And what browsers do we support?

The reasoning for not adding babel is the same for TypeScript: bundle size This is a small lib, don’t think we would benefit a lot using Babel.