pinojs/pino

Add docs page: Switching from bunyan

Open

#727 opened on Oct 10, 2019

View on GitHub
 (4 comments) (3 reactions) (0 assignees)JavaScript (13,157 stars) (839 forks)batch import
documentationgood first issuehelp wanted

Description

I found Pino when googling for bunyan alternatives, because I'm hoping to replace bunyan in a Node web server project I've inherited.

It would be useful if Pino could add a "Switching from bunyan" docs page as a starting point for people in this position, to list any important conceptual differences and to map bunyan concepts to corresponding Pino concepts.

Contributor guide

Tech stack
javascriptnodejs
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
familiarity with bunyanbasic knowledge of pino
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
Review existing Pino documentation structure (e.g., docs/ folder) and bunyan's migration guide if any. Create a new markdown page in the docs directory that compares bunyan and Pino concepts, such as log levels, serializers, child loggers, and transport mechanisms. Include code examples showing how to migrate common bunyan patterns to Pino. Consider asking maintainers if there is a preferred section for this guide.