Document formats for logs
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- node.js
- Domain
- documentation
Research direction
Start by reviewing the existing Node.js guidance and the linked Winston recommendation. Research suitable log formats for HTTP services and CLI applications, then document specific recommendations for both contexts; the work is done when those formats are clearly described.
Written by the indexing model from the issue text.
Description
We recommend winston, but we could also recommend specific formats for logs, both for HTTP services and for CLI applications.
h/t @tidoust
- Dominant language
- No language data
- Stars
- 13
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from w3c/nodejs
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
documentation question
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
documentation question
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100