wood1986 / ln Goto Github PK

Hello,

The ln console output displays an extra newline per line of text, which makes it unsightly and less readable. The JSON output, on the other hand, is data intended to be read programmatically, thus doesn't necessarily need the carriage return.

Removing the "\n" (or switching appender.write, and selectively appending the "\n" for file output only) would resolve this issue.

I did not see any documented setting allowing users to specify if the console appender should log to STDOUT or STDERR.

I got below error when I tried to log with cluster. I might be making some mistake. Can you please provide a sample example for logging with cluster/workers.
Error: ENOENT, open '../logs/error/log.1506011842' at Error (native) events.js:85 throw er; // Unhandled 'error' event

Clever code, thanks for this.

If you were to queue your log strings when the user calls log.info(...) rather than on the emit('log', ...), you could achieve a reduction in number of calls to stream.write, right?

Thanks for the great work!

I have a appender for Logentries (https://logentries.com/) and for this JSON string is perfect. However, I like to log only messages to console, not entire JSON string.

It would be great if it is up to appender to decide what format to render JSON object.

Another justification is that I need to access "level" of logging. In order to achieve this, I need to parse JSON string, which is unnecessarily expensive operation if it was JSON object, with the current implementation.

For example, I should be able to do something like this if it was JSON object:

appender_logentries.emitter.on("log", function (appender, timestamp, log) {
logger_logentries.log(log.l, JSON.stringify(log))
});

appender_console.emitter.on("log", function (appender, timestamp, log) {
if(log.l === 10) console.log(log.m)
if(log.l === 20) console.warn(log.m)
if(log.l === 30) console.error(log.m)
...
});