chalk VS node-config

4. Chalk

Chalk: Provides an easy way to stylize terminal strings with various colors and text formatting in Node.js, aiding in creating visually appealing command-line outputs

Chalk is a popular choice for adding colors to CLI output while maintaining readability.

Librerías: Chalk winston, log4js

Today the most popular library and de facto standard is the chаlk. The chalk has rich functionality, is fast but not ideal. It lacks some useful features.

This is a new tutorial on how to create a command line interface application, and our application today is a Mortgage Calculator. I used in this program packages such as 1- inquirer for interactive questions and answers: https://www.npmjs.com/package/inquirer 2- Sqlite3 DBMS 3- Chalk for colorful output in the terminal: https://www.npmjs.com/package/chalk

One of the libraries I used most that went full-ESM is Chalk. They released v5 over a year-and-a-half ago (November 2021) with ESM-only support and haven't updated v4 - their last iteration that supported CommonJS - since. If you go into their GitHub Issues section, you'll see a number of issues raised about CommonJS support, most of which are just responded to with a link to a post they made about switching over. Fair enough. I guess if I had to constantly answer the same question over and over, I might do the same.

To colorize my logs, I used a chalk package and created a logger utility:

We will add some dependencies to help us deal with CLI behaviours (inquirer) and text coloring (chalk).

node-config

This will allow to set a security operation mode and configure the channels. I chose to use the config package as I had good experience with it and it supports cascading config options.

Tailwind CSS v3.2.4 includes a new @config directive that lets you specify which Tailwind CSS config to use for that file.

Use https://www.npmjs.com/package/config so you can have runtime variables accessible based on provided json's

I am using this node-config package (https://github.com/node-config/node-config) in my project. I feel like I am brute-forcing my way, is there a better way to do this? Any hint would be appreciated or just point me in a direction that would be great. Thank you!

In this article, I'm going to demonstrate how the dotenv and node-config NPM packages can be used together to keep your Node.js application code organized across environments.

#3 Environment-specific config files with Config package

I always disliked the .env file. Almost every time I was forced to place it on the top level of my app directory. At some point i started to use the npm config package. This gives the application a consistent configuration interface and there is a formidable way to implement it into the NextJS environment. For people which prefer code over text, feel free to checkout the finished implementation.

How do I handle configs? In our Node APIs we use this config package, which allows us to override default configs on a per-environment basis. What's the standard way of doing this in Go?