chore: updates docs and example to use transports

[aaestrada]

Uses thread-stream to create a single worker to forward data to all target destinations

Note we will need to resolve the issue at hapi-pino.

[aaestrada]

Node js profile test no1

Node js profile test n2

[mannyluvstacos]

Looks like updating the unit tests for index.test.js should have the tests running 💯 again.

🤝

Long Live Catalyst 🚀✨🌕

[aaestrada]

Looks like updating the unit tests for index.test.js should have the tests running 💯 again.

🤝

Long Live Catalyst 🚀✨🌕

Thanks @mannyluvstacos! I will review the unit tests once my code is ready! I wanna use the manifest.json to register this code instead the index.js file.

[aaestrada]

Node js profile test no1

Node js profile test no2

[mcjfunk]

This PR is not doing what the title says. It is only adding an example for how to use transports with pino-pretty in local development.

[aaestrada]

node js profile for pino-http-print no 1

node js profile for pino-http-print no 2

[aaestrada]

node js profile for pino-pretty no 1

node js profile for pino-pretty no 2

[mcjfunk]

See comment. Also, when squashing and merging, we should update the commit message to be something like: chore: updates docs and example to use transports for pino-pretty

[mcjfunk]

Do we really want to advertise this approach? What is the advantage here? pino-rotating-file is similarly in its own process plus it supports log rotation. Can/should we just show that in the Readme rather than create examples that we need to keep updated?

[shellbj]

Do we really want to advertise this approach?

Not really.

What is the advantage here?

It cleaned up some of the configuration in the example and docs to show how to move pretty into a conditional transport.

@vrbo/pino-rotating-file is similarly in its own process plus it supports log rotation. Can/should we just show that in the Readme rather than create examples that we need to keep updated?

This and update the example/default to use a pino/file transport for stdout.

[aaestrada]

Yes! this pr will help our developers a quick and easy way to transport and transform logs for production...

if necessary, the examples serve as a guide/introduction to make a more advanced configuration.

[mcjfunk]

Looks good. Just a reminder... when squashing and merging, please update the commit message to be something like: chore: updates docs and example to use transports

[github-actions]

🎉 This PR is included in version 5.3.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀