Open
Conversation
Add a comprehensive migration guide for developers switching from Bunyan to Pino, covering: - Basic setup differences - Log levels mapping - Child loggers - Streams vs transports - Pretty printing - Serializers - Request logging - Output format differences Fixes pinojs#727
jsumners
requested changes
Feb 3, 2026
Member
jsumners
left a comment
jsumners
left a comment
There was a problem hiding this comment.
"Pino" is not properly name cased throughout the doc.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a comprehensive migration guide for developers switching from Bunyan to Pino.
The guide covers:
This helps developers who found Pino while looking for Bunyan alternatives to migrate their existing codebases smoothly.
Fixes #727