i18n-node VS debug

One great tool for inclusion is the i18n package helping us develop multi language apps with minimum effort.

If you plan to create a multilingual version of your app, you should use one of the Node.js internationalization libraries available, for example on Openbase. This article will cover the i18n-node as an example. You may choose another library according to your preferences. They do implement localization functionality pretty much in the same way.

Great Work ! Kudos 👍. Just a suggestion that as you are building something which has a worldwide audience scope you might need to add language support which might not be very difficult with you current tech stack. You can use i18n package .

You have to maintain translation keys. Lookup i18n. This is a js lib for example: https://www.npmjs.com/package/i18n

Or the developer can save everyone the effort and just import an NPM package for it: https://www.npmjs.com/package/i18n

Take a look at the industry standard i18n

Have you considered why this would be used rather than a internationalization package such as https://www.npmjs.com/package/i18n? Also adding the ability for language translations to the snippets would be awesome 🙂

Explore i18n

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)

A lot of tools rely on the NODE_ENV environment variable for that, React included. Another great package that’s pretty popular is https://www.npmjs.com/package/debug You can create namespaces and then filter the logs you are interested in.