listr VS Inquirer.js

I’m gonna make a console based application, asking user to make some choices, kicking off some async tasks, giving feedback etc. I’ve found inquirer and listr for handling part of this.

Major shoutout to listr + listr2 for being the motivation and visual inspiration for Tasuku, and for being my go-to task runner for a long time. I made Tasuku because I eventually found that they were too structured and declarative for my needs.

Remember the IF ELSEIF we had setup for arguments? Let's add a --help argument that lists out all the commands. Lists are a very important part of CLIs. I'm using a helpful package listr to handle these lists. Let's add the following code into our file in the place where we have our IF checks.

Basic things you should learn: - Dom manipulation - Http calls - Rxjs/promise - server side/ client side js - how frameworks use it - write script with listr (https://github.com/SamVerschueren/listr)

Inquirer.js is a handy tool for adding interactive prompts to your CLI.

There is a CLI application based on Inquirer. Potentially, it could be another CLI library, say something from the following list. Our goal is to provide integration tests. But before that, let's look at the related terminology.

inquirer

If you boil plop down to its core, it is basically glue code between inquirer prompts and handlebar templates.

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

We can easily achieve that with the inquirer package. This package allows you to ask different types of questions, such as input questions (open-text questions), confirmation questions (Yes/No), etc.