Effective Error Logging: Capturing Stack Traces Without Unwanted Recovery

is there a better to way log errors in a way that allows you to see the stack trace?
I had basically a

catchAll(Console.error)

catchAll(Console.error)

catchAll(Console.error)

catchAll(Console.error) which was just loging out

{
  _id: 'ParseError',
  message: 'Expected ... actual null'
}

{
  _id: 'ParseError',
  message: 'Expected ... actual null'
}

{
  _id: 'ParseError',
  message: 'Expected ... actual null'
}

{
  _id: 'ParseError',
  message: 'Expected ... actual null'
}

which was actually quite unhelpful because there were like 5 places it couldve come from

if I

catchAll((e) => Console.error(e.toString()))

catchAll((e) => Console.error(e.toString()))

catchAll((e) => Console.error(e.toString()))

catchAll((e) => Console.error(e.toString())) then I get the tree formatted version of the error

{ ... }
└─ ["text"]
   └─ is missing

{ ... }
└─ ["text"]
   └─ is missing

{ ... }
└─ ["text"]
   └─ is missing

{ ... }
└─ ["text"]
   └─ is missing

and only when I

catchAllCause((e) => Console.error(e.toString())

catchAllCause((e) => Console.error(e.toString())

catchAllCause((e) => Console.error(e.toString())

catchAllCause((e) => Console.error(e.toString()) I get the trace

Expected { ...}, actual null
    at <anonymous> 
    ...

Expected { ...}, actual null
    at <anonymous> 
    ...

Expected { ...}, actual null
    at <anonymous> 
    ...

Expected { ...}, actual null
    at <anonymous> 
    ...

but now im recovering from defects I dont want to

No replies yetBe the first to reply to this messageJoin