Warning : prettyPrint is deprecated, use the pino-pretty transport instead
See original GitHub issueI upgrade to canary (0.37.6-canary.57) on my project. Every time I make on update on the codebase, I got :
[PINODEP008] PinoWarning: prettyPrint is deprecated, use the pino-pretty transport instead
This came from the upgrade of Pino to V7 #3588 https://github.com/pinojs/pino/blob/master/docs/api.md#prettyprint-boolean--object
The prettyPrint option is deprecated, but everything seem to still working. The solution is to use pino-pretty transport, which will came with #3298
Do you feel that it is a priority to fix this ?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
0 - Stack Overflow
[PINODEP008] PinoWarning: prettyPrint is deprecated, look at https://github.com/pinojs/pino-pretty for alternatives. What to do? App is crashing
Read more >pino-pretty - npm
Start using pino-pretty in your project by running `npm i pino-pretty`. ... page due to the deprecation of the prettyPrint option of pino ......
Read more >A Complete Guide to Pino Logging in Node.js - Better Stack
In this tutorial, you will learn how to create a logging service for your application with Pino. We'll discuss many of the features...
Read more >V0.38 Upgrade Guide - RedwoodJS Community
Many upgrade steps can be completed using the @redwoodjs/codemods ... prettyPrint is deprecated, use the pino-pretty transport instead.
Read more >Readme
Very low overhead Node.js logger. Documentation. Benchmarks ⇗; API ⇗; Browser API ⇗; Redaction ⇗; Child Loggers ⇗; Transports ⇗ ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Good heads up @simoncrypta I think we’re good until v0.38 comes out (which is likely next week).
Closing this but looping in @dthyresson for additional thoughts (and to reopen if needed).
We already do it because we retain default pretty print options, right? The problem is we will force one way of doing logging in dev. It can be okay, we can also add
LoggingDev
property tocreateLogger
who will overwrite our default transport in dev (pretty print to the stdout).