pino VS ms.js

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

Vitest is for frontend. Jest is not good for backend (I don’t like it for frontend either), take a look at this issue.

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

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

Use a configurable logger like pino

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:

Number of dependencies: one way to tell if a library is not too challenging to be used as study source is based on the production dependencies count. The fewer the better. For example, I chose debug because it only has 1 dependency (ms), while the rest of the code relies on core NodeJS modules - which is exactly what I was looking for - to learn how to build a library from scratch, not off the shelf libraries with many external deps, which in turn are based on more deps. There you go, dependency hell.

8.ms

For recurring habits I just store an ms string, when I tick something off it adds that time for the next time it's due. Easy peasy.

Next.js Redux Toolkit Framer Motion Tailwind Radix UI Radix colors react-use clsx lodash ms

I've been fighting this in many places, but of course there are fools out there who actually defend this practice rather than be indifferent to it at worst. Fixing it in those two places would actually fix about 70–80% of all such instances, since many websites just depend on those libraries. Feel free to upvote them, respectively.

The final and most important function of our Lambda, the loadParameters function accepts a single value named expiryTime that is by default set to 1 hour and can be overridden. I have used the ms library to set human readable time periods which will be automatically converted to milliseconds.