Matteo Collina

Don't use console.log, use pino.destination() instead (otherwise you loose all the benefit of worker_threads).

pino-pretty is _not_ deprecated, only the `prettyPrint` option. The following would do what you want: ```js const pino = require('pino') const transport = pino.transport({ target: 'pino-pretty', options: { destination: 1...

I don't understand the question, could you clarify?

Thanks for the long explanation @seprich! I would love to implement such feature, however it would cause a massive slowdown. As soon as https://github.com/pinojs/pino/pull/1003 lands and v7 is released, you'll...

> Or the new v7 transport is stackable ? Not as they are in the PR but I think we might add some API to do that as it seems...

I think @davidmarkclements would be highly pleased by that view. That's what I have in mind.

Would you like to send a Pull Request to address this issue? Remember to add unit tests.

What are you using on the graphql side? have you got an example? I don't think it's possible to get the resolvers called.

I think you should develop a serializer that is apollo-specific (possibly in a different module).

Unfortunately so. We do not think it is needed either as prettyPrint is just something for development - so we did not implement it. If you would like to work...