tracer for node.js VS loglevel

Tracer calls itself the customizable and powerful logging library for Nodejs. With Tracer, you can print simple logs, colored logs, and even set output levels. You can customize it by printing a timestamp, file name, line number, and even the call stack! The list is huge!

A relatively popular, simple, “minimal and lightweight” Node.js logging library that works both in the browser and for Node.js. According to its documentation, the LogLevel Node.js logging libraries seek to replace the console methods with more features such as the “ability to disable error logging in production and filter logs by their severity”. LogLevel is a Node.js logging library that has no dependencies and can continue logging even in browsers that don’t have support for the console object. Like other Node.js logging libraries, LogLevel is also extensible and offers log redirection capabilities, formatting, and filtering. For developers that develop in TypeScript, LogLevel already has included type definitions making it even more convenient to use.

I'm using Node.js, NPM, ngrok, express and whatsappcloudapi_wrapper, as well as pdfkit, uuid, node-fetch v.2, loglevel.

The problem in my case is that TypeScript is actually right :) https://github.com/pimterry/loglevel/blob/master/index.d.ts "Not all constituents of type 'RootLogger' are callable" and it's true.

loglevel