Cliffy
NodeJS Framework for Interactive CLIs (by drew-y)
Commander.js
node.js command-line interfaces made easy (by tj)
Our great sponsors
Cliffy | Commander.js | |
---|---|---|
1 | 44 | |
347 | 26,072 | |
- | - | |
0.0 | 8.7 | |
almost 2 years ago | 12 days ago | |
TypeScript | JavaScript | |
ISC License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Cliffy
Posts with mentions or reviews of Cliffy.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-02.
-
Is Node.js a good way to implement a CLI app with persistence?
Due to Node's asynchronous behavior, it makes Node great for long-running processes that make a lot of HTTP requests, database calls, and other async ops, like a web server or a REST API. However, if I am making a CLI tool for pretty much personal use only, with very minimal async operations, then blocking the event loop with a synchronous function that will resolve almost immediately will make no difference perceivable to a human brain or have any speed benefits that someone can actually observe (think `fs.readFileSync` or `require('dotenv') of 10 line config file, or a quick embedded db (sqlite) query with only ~100 records. I'm wondering what the best way to implement the database part of the app synchronous. I can read/write to JSON files but it would be tricky because the data is relational, and some complex joins and other data wrangling operations are required (complex to perform in JS but are easy to implement in a SQL statement). It's not important what the operations are, that's not the point of this post. This is mostly a personal project of interest: making this CLI tool completely avoiding any async operations/using no promises. I would like to use node tho, as I said this is just out of interest and I also want to experiment with several CLI libraries such as Ink or Cliffy.
Commander.js
Posts with mentions or reviews of Commander.js.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-03-23.
-
Developing a Node CLI App in an NX monorepo
Visit the Commander.js reference.
-
Next.js Codebase Analysis <> create-next-app <> index.ts explained — Part 1.3
In the previous article, I looked at a Commander to configure and accept cli options and assign it to a variable called program.
-
[AskJS] Looking for JS course for experienced developers?
You can write a command line utility using zx or commander.js. Hit a public api, spit stuff out in the console, etc.
-
[AskJS] What is your preferred solution to share and execute Node.js scripts ?
In your index.js you can do whatever you want, even create an interactive CLI (check commander).
-
Exploring video generators in FFMPEG
There is clearly a whole load of repetition, so this should be fairly easy to build and parameterise. Essentially this will all just be string building so we won't need to use any particular libraries for most of this script. We will need a way to call ffmpeg though - and ffmpeg will need to be present too, of course. To call a CLI command we can use the package commander.
-
How to Create a Testable CLI using TypeScript?
Commander.js is an NPM package that makes it easier to build CLI tools. You can find its documentation over here
-
Creating a Node.js Command-line Tool, Linux Terminal CLI and NPM Package
You can also use npm package commander to make more complex command line tool with lot of options and sub commands.
-
Create a Node.js command-line library with NRWL NX workspace
commander - npm - Required. A library that lets you define the commands and their arguments, options, help, etc.
-
Releasing package to npm
Throughout my time writing and updating my static-site generator, I've been using npm from the very foundation I use an npm package called commander. Therefore, it is obvious that for the tool that I will be using to publish my ssg, I will do so with npm.
-
Building a TypeScript CLI with Node.js and Commander
The command line has thousands of tools, such as awk, sed, grep, and find available at your disposal that cut development time and automate tedious tasks. Creating a command line tool in Node.js isn't very complicated, thanks to a powerful library like Commander.js.
What are some alternatives?
When comparing Cliffy and Commander.js you can also consider the following projects:
oclif - CLI for generating, building, and releasing oclif CLIs. Built by Salesforce.
listr - Terminal task list
Ink - 🌈 React for interactive command-line apps
zx - A tool for writing better scripts
cli-table3 - Pretty unicode tables for the command line
Bit - A build system for development of composable software.
terminal-image - Display images in the terminal
cli-truncate - Truncate a string to a specific width in the terminal
chalk - 🖍 Terminal string styling done right