Loguru VS debug

Because you get to see the simultaneous mix of arguments about objective verifiable facts and arguments about yelling at each other. Plus I don't understand how to cook but I do understand Delgan/loguru#563.

How can we integrate with current logging libraries such as logging, logges, loguru? And how would you compare your library with ic

I found loguru online and was thinking if it's relevant for my code. As far as I understand it would be preferable as opposed to me printing my exceptions with print.

You should try the loguru library. I was able to roll a rolling-upload-to-s3 adapter in under an hour. Switching to json logs is one bool flag away. Plus it's gorgeous

https://github.com/Delgan/loguru

Also iirc s3's "file-like interface" does not actually obey the file protocol, which is obnoxious.

If you have a choice, save yourself some heartache and install loguru

This? First time to hear about it. Thanks!

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.

Another way to solve this is to have the logs in place, but only enable them conditionally. If you enable all the logs are the time, you only get a lot of noise that won't help you. If you are using JavaScript, you can use the package debug to add logs that are active by the DEBUG environment variable.

I'm using the debug package: https://www.npmjs.com/package/debug, but some reason I don't see millisecond diffs, which would be really useful.

Although it's used by Express, it's indeed more broadly, the way a popular NPM package called debug works, which is used internally in Express too. Under the hood, the debug package expects the DEBUG environment variable to determine what debug messages to print (could be on the console, or into a file, or into stdout to be collected by a log aggregator service).

Finally, if they're logs you want to be able to inspect in production without printing them to the console by default, you can use debug.

It is a drop-in, TypeScript replacement to enhance the widely popular https://www.npmjs.com/package/debug (230k weekly downloads).

debug - npm - Required. A popular library to write debug logs.

I strongly recommend using the debug package from NPM to organize your log messages

Use the [debug npm library](https://www.npmjs.com/package/debug) to disable your logging unless someone provides the right environment variable (e.g. DEBUG=* which enables all logging)