Pinned issues
Issues
- 7
Any plan for connector to nitro?
#1855 opened - 4
Any chance to use log level strings ("warn", "info") as for value of "level" with multiple targets
#1854 opened - 2
- 5
Pino-pretty as a transport target causes `--require` modules to be loaded multiple times
#1852 opened - 1
- 3
log message along with object
#1850 opened - 1
Incorrect child-child benchmark
#1848 opened - 1
- 23
Pino stopped writing logs
#1845 opened - 2
Bun support?
#1842 opened - 7
- 1
Type errors when using `log.child()`
#1840 opened - 4
passing logger methods to a function (2)
#1839 opened - 4
[mergingObject] under custom property
#1838 opened - 6
- 4
- 2
Logger options type
#1835 opened - 2
Missing msg property
#1833 opened - 0
[question] How to setup level for pipeline?
#1832 opened - 2
pino-datadog-transport return deprecated warning
#1830 opened - 8
Pino stopped writing logs
#1829 opened - 11
Memory Leak Pino, Pino Http, & Pino Pretty
#1823 opened - 4
Deep debugger integration
#1821 opened - 6
Pino reliability
#1820 opened - 7
Logging Axios error crashes server
#1817 opened - 3
Regression in Pino browser 8.14.1 > 8.14.2
#1816 opened - 4
- 5
- 8
broken on Node 16 & 18
#1809 opened - 2
Consideration: Auto completion for level option
#1807 opened - 3
validateOptions function
#1806 opened - 9
Looping over undefined when using transport
#1805 opened - 4
- 2
- 2
- 2
- 2
- 4
Cannot resolve worker_threads
#1794 opened - 2
- 2
Named export not available for browser.js
#1792 opened - 2
- 6
Duplicate message keys from logMethod hook
#1790 opened - 2
"Module did not self-register" on Heroku
#1789 opened - 3
- 16
- 3
- 5
- 8
Memory leak after logging ~26 million lines
#1781 opened - 3
Question regarding creating transport pipeline
#1776 opened - 4