consola VS pino

Console logs are not always well structured and eye-pleasing. Unpleasant and messy console takes away from the bliss of a developer. I recently came across a package named consola which does exactly this — making consoles meaningful and elegant.

consola library is a great alternative to JavaScript console. Provides some really neat formatting and more power features.

https://github.com/unjs/consola

Fastify comes with Pino by default, but logging must be enabled for it to work:

Learn more about logging in Fastify and how to customize the Pino logger.

The Fastify framework includes the Pino logger by default (a really great logger with lots of cool features that doesn't compromise on performance). The framework itself allows a lot of really cool stuff, like controlling the level of logs at runtime.

Fastify provides a built-in logging mechanism based on Pino that allows you to capture various events in your applications. Once enabled, Fastify logs all incoming requests to the server and errors that occur while processing said requests. It also provides a convenient way to log custom messages through the log() method on the Fastify instance or the request object.

1. pino

Have a look at https://github.com/pinojs/pino

NodeJS -> Pino, Winston, Bunyan, Npmlog, e.t.c.

Using pino as a logger, for every request on the _server_ , a unique ID generated client side in the headers, so a log may be something like:

pino (logger)

Pino is also a popular Node.js logging library alternative for developers. There are claims that it is 5x faster than other Node.js logging libraries besides providing standard features such as the ability to choose a storage medium, log levels, and formatting capabilities. Pino is also highly extensible, flexible, and easy to integrate with Node.js frameworks such as Express, Fastify, and Restify. The library is a low-overhead Node.js logging library and supports asynchronous logging despite being fast. Pino also gives you the ability to create child loggers.