Terry Moore

You should be able to send it to `logdna.error()` and if the message is an `instanceof` `Error` then it will send it to `captureError`

I am not a react expert but I am guessing that adding the logger init function in `useState` is causing the logger to get initialize more than once. [Here](https://github.com/logdna/logdna-browser/blob/main/examples/react-example/src/index.tsx) is...

you will probably need to add the `env` to the `logdna.addContext({})` method. https://github.com/logdna/logdna-browser#add-custom-metadata-for-log-lines

@BryantDavis1986 I just browsed through our logs and noticed that its not there either. I have a feeling the logger doesnt currently support this. I will make a ticket to...

This should be able to be accomplished by adding a custom `beforeSend` [hook](https://github.com/logdna/logdna-browser#beforesend). This will parse both the `message` and the `lineContext` ``` const jsonReplacer = (key, value) => {...

@rfink True, you could `require/import` ` fast-safe-stringify` or any other stringify package and use it in your hook. We mostly use ` fast-safe-stringify` because of its circular reference detection.

@stephent Thank you for reporting this. I will read up on the issues that you posted and try to reproduce the issue.

@stephent From what I have found out the issue is that the library we (and pino) use to handle the circular references is unable to handle large objects with deeply...

@joeyfigaro Thanks for checking out our node logger! We definitely hear you out on having something that's more frontend/React-Native friendly. It's something that we are currently looking into and would...

I have a similar issue with react-native-trackplayer/swiftaudioex. I am developing a music app that plays live shows in which users expect a seamless (or near seamless) transition between songs but...