Resolved/invalid issues to close

[VladimirMikulic]

While exploring issues list, I noticed a lot of issues don't apply anymore or have been resolved but not closed so I thought I'd compile this list so you can close them:

• Documentation: Help > Exit logging dead link #1600 (resolved)
• LTS doc needs to be updated #1485 (resolved)
• Error: "fn is not a function" while setting up a pino transport via pipeline #1383 (third party package issue)
• adding Pino to global #1258 (question answered by maintainers)
• Question: Transform entire log JSON format #1248 (question answered by a maintainer)
• [Question] How to get a trace log similar to console.log? #1052 (question answered by a maintainer)
• prettyPrint does not print child object e.g. x-request-id #1043 (prettyPrint option no longer exists)
• Clarify prettyPrint documentation #835 (prettyPrint option no longer exists)
• A broken link in readme.md #805 (resolved)
• Best practice: Prettify both HTTP request logs and "normal" log messages #651 (resolved)
• Improve prettifier documentation #510 (prettyPrint option no longer exists)
• Thoughts on recommending Cabin for more sensitive and automated data Redaction? #850 (PR closed)

[mcollina]

Thanks, all closed now!

[VladimirMikulic]

Recently, I had some more time to triage those old/invalid issues.
Here's the new batch for you @mcollina

• What is the recommended way for library authors to use pino? #1603 (question answered by a maintainer)
• Browser side usage: "browserify" and/or browser.js ? #1585 (question answered by a maintainer)
• pino.multistream is not a function #1552 (original issue resolved)
• Logging to a JSON array and parsing it with pino-pretty, is this the correct approach? #1528 (can be closed with link to https://getpino.io/#/docs/transports?id=writing-a-transport)
• logging request / response headers from fetch #1524 (very vague description, no further details)
• Can't use custom levels in multistream with TypeScript #1595 (duplicate of Support customising levels for multiple transports #1538)
• Sorting order of key in log object #1504 (question answered by a maintainer)
• Change Log Level for root and children #1330 (resolved in Added onChild callback with tests and documentation #1541)
• [question] How to create custom destination based on log level #1271 (resolved in feat: add dedupe option to transport #1640)
• Should formatters and timestamp be done with transport? #1213 (question answered by a maintainer)
• Provide solution for creating custom loggers easily #1100 (question answered by a maintainer)
• update docs/legacy.md #1041 (resolved/not relevant anymore)
• graphql request formatting #1022 (question answered by a maintainer)
• Time benchmarks and measuring #1011 (question answered by a maintainer)
• Understanding how formatters and serializers work #991 (vague description, no further reproduction)
• Adding requestId prefix to lamda logs ahead of json #648 (resolved / issue reported settled on a solution)

[mcollina]

thx!

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.