Hi, thanks a bunch for this project. Super helpful.
Right now, when passing Error objects in the meta parameter they get logged as {} because of the design of the Error object (as you know doubt know).
const log = require('lambda-log')
const error = new Error('foo')
log.warn('Heads up!', {error})
// {"_logLevel":"warn","msg":"Heads up!","error":{},"_tags":["log","warn"]}I can use log.options.replacer to get a much better serialization of the Error object (using the error-to-json package here):
const log = require('lambda-log')
const errorToJson = require('error-to-json').default
log.options.replacer = (key, value) => {
if (value instanceof Error) return errorToJson(value)
return value
}
const error = new Error('foo')
log.warn('Heads up!', {error})
// {"_logLevel":"warn","msg":"Heads up!","error":{"name":"Error","message":"foo","stack":"Error: foo\n at REPL9:1:15\n at Script.runInThisContext (vm.js:120:18)\n at REPLServer.defaultEval (repl.js:442:29)\n at bound (domain.js:427:14)\n at REPLServer.runBound [as eval] (domain.js:440:12)\n at REPLServer.onLine (repl.js:777:10)\n at REPLServer.emit (events.js:326:22)\n at REPLServer.EventEmitter.emit (domain.js:483:12)\n at REPLServer.Interface._onLine (readline.js:329:10)\n at REPLServer.Interface._line (readline.js:658:8)"},"_tags":["log","warn"]}My suggestion is to consider making this the default behavior. Are there any use cases where serializing an Error to {} would be the better behavior?
Thanks again for the project!
Hi, thanks a bunch for this project. Super helpful.
Right now, when passing
Errorobjects in themetaparameter they get logged as{}because of the design of theErrorobject (as you know doubt know).I can use
log.options.replacerto get a much better serialization of the Error object (using the error-to-json package here):My suggestion is to consider making this the default behavior. Are there any use cases where serializing an
Errorto{}would be the better behavior?Thanks again for the project!