-
Notifications
You must be signed in to change notification settings - Fork 878
Issues: pinojs/pino
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[bug] in the browser,
pino.stdSerializers.errorWithCause
does not serialize cause
prop
#2057
opened Oct 10, 2024 by
jorroll
isLevelEnabled not working in v9.3.1 and v9.4.0.
bug
#2053
opened Oct 2, 2024 by
elevatedbuttonpusher
The
pino.destination()
function is not defined on a browser (bug and/or documentation issue)
#2032
opened Aug 20, 2024 by
zeel01
Print warning on changing log level when using multistream
bug
good first issue
#2030
opened Aug 18, 2024 by
rluvaton
[bug] logger.
setBindings
undefined when using esm exported pino
bug
#2021
opened Aug 5, 2024 by
ryuujo1573
Error: unable to determine transport target for "@baselime/pino-transport"
#2019
opened Jul 31, 2024 by
jacobsamo
Improve generics for Logger, LoggerOptions, LogFn and WriteFn
#2011
opened Jul 19, 2024 by
emilio-toledo
stdSerializers
cannot be avoided for Request and Response
enhancement
#1991
opened Jun 15, 2024 by
gerardolima
How should a Pino instance be identified in runtime?
#1984
opened Jun 3, 2024 by
gerardo-lima-moonfare
Logs missing in debugger console using node --inspect
help wanted
#1983
opened Jun 3, 2024 by
richterdennis
Previous Next
ProTip!
Updated in the last three days: updated:>2024-11-06.