Mar 29, 2022

Create CLI apps the easy way with cac in less than 50 lines

I’ve never built a CLI app before, but when I was building the helper CLI tool for Hyperdocs, I realized that building CLI apps are not hard at all! Before building the CLI, I did a lot of research about the available tools and I’ve figured out the best way to build CLI apps that I never came across in any of the available blogs/tutorials on internet. So I just thought of writing one!

Let’s see how to create a simple CLI app to shorten links.

We will be starting from scratch i.e just with an empty folder to a perfect dev workflow where you can preview commands of cli as you code them and publishing it to npm and managing releases on GitHub.

Here’s are the features of our CLI app

I’ll call mine - Linkk


What are we building

Linkk Demo

Let’s start

Run npm init without the -y flag so that you can set up the required fields in package.json

This is what I had to do for linkk

npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sensible defaults.

See `npm help init` for definitive documentation on these fields
and exactly what they do.

Use `npm install <pkg>` afterwards to install a package and
save it as a dependency in the package.json file.

Press ^C at any time to quit.
package name: (linkk)
version: (1.0.0) 0.0.0
description: A simple tool to shorten links from CLI.
entry point: (index.js) dist/index.js
test command:
git repository:
keywords: link-shortener, url-shortener, linkk, url, link
license: (ISC) MIT
About to write to /Users/kishore/Documents/Lalit/Coding Projects/Web Development/linkk/package.json:

  "name": "linkk",
  "version": "0.0.0",
  "description": "A simple tool to shorten links from CLI.",
  "main": "dist/index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  "repository": {
    "type": "git",
    "url": "git+"
  "keywords": [
  "author": "Lalit",
  "license": "MIT",
  "bugs": {
    "url": ""
  "homepage": ""

Is this OK? (yes) y

Installing dev dependencies

To build the app, we will be requiring some devDepencies

Make sure you install all these so that we can get started easily

Set up

Let’s set up some scripts in package.json


Although we can publish npm packages without bundling, we will be doing it so that we ship a single file in the package and tsup uses esbuild under the hood, so you don’t have to worry about waiting for the build.

So add "build": "tsup src/index.ts --format cjs,esm --clean --minify",

This points tsup to the index.ts under src directory and asks it to bundle it into cjs and esm formats and also it asks tsup to clean and minify the output


This command helps re-bundle the code after each save of the file. Re-bundling happens in the blink of an eye as it uses esbuild under the hood.

This is just the build command with a --watch

tsup by default bundles and saves the output to dist/ directory

Here’s how my final scripts field in package.json

"scripts": {
    "build": "tsup src/index.ts --format cjs,esm --clean --minify",
    "dev": "yarn build --watch",
    "prepublish": "yarn build",
    "test": "echo \"Error: no test specified\" && exit 1"

Adding .npmignore

.npmignore let’s you have a fine grain access of what’s going to get published on npm registry

We will be just adding node_modules/ to it.

Editing package.json

Add these fields to package.json

"main": "./dist/index.js",
"module": "./dist/index.mjs",
"type": "module",
"exports": {
  ".": {
    "require": "./dist/index.js",
    "import": "./dist/index.mjs"
"bin": "dist/index.js"

Once we bundle the src/index.ts, tsup will place the output in dist/index.js file. The main field points to this file here. Read this blog to find out more about bundling your code.

Setting up shorten command

We will be using the’s free api to shorten links without any auth.

So let’s create the src/index.ts file. This is where the main logic of the app resides.


We should be adding shebang to the top of the main file to use node while executing the code.

// index.js
#!/usr/bin/env node


To see how the CLI works, you must first link it with yarn or npm. This just takes a single command:

npm link

or with yarn

yarn link

This lets you use the package anywhere in your device w/o installing. Now you can run linkk shorten <link> and check if this works.

Using cac

If you have never built a cli app before, I recommend getting started with cac. This is a much smaller and simpler alternative to other libraries such as commander.js.

import cac from "cac";

const cli = cac();

  .command("shorten <link>", "Shorten a link")
  .action((link) => console.log(link));


This code above creates a shorten command for our cli app with a link input. And once the linkk shorten command is used we will be logging it to the console.

Let’s build the main logic now`${link}`).then(({ data }) => {
  // Stop loader
  // Copy short link to clipboard
  // Log shortened link to console

Checking for valid url

We will be using the is-url library to check if the provided string is a valid link or not.

If the string is not a valid url, the app quits with an error message.

The error message is coloured in red with the help of the chalk library

import isUrl from "is-url";
import chalk from "chalk";

if (isUrl(link) === false) {
  console.error("Please provide a valid URL"));

Loading spinners

To display loading spinners, we will be using the loading-cli library.

import loading from "loading-cli";

const load = loading("Shortening link...").start();

shorten(link).then(() => {

Copying to clipboard

Let’s use clipboardy to copy the shortened link

import clipboardy from "clipboardy";

shorten(link).then(() => {


Now we saw different pieces of code in the main src/index.ts file, let’s combine them now

#!/usr/bin/env node

import axios from "axios";
import cac from "cac";
import chalk from "chalk";
import clipboardy from "clipboardy";
import isUrl from "is-url";
import loading from "loading-cli";

const cli = cac();

  .command("shorten <link>", "Shorten a link")
  .action(async (link: string) => {
    if (link.startsWith("http") === false) {
      link = `http://${link}`;

    if (isUrl(link) === false) {
      console.error("Please provide a valid URL"));
    const load = loading("Shortening link...").start();
      .then(({ data }) => {

        const shortLink = `${data.result.code}`;

        console.log("Shortened! Copied it to clipboard too!"));

        // copy to clipboard

        console.log(` ${shortLink} `));

        console.log(`Other links:
- ${}
- ${}
- ${}`);


Now that we are done with the code, it’s time to publish it to the world so that everyone can start installing and using this.

For publishing packages and maintaining releases in the future, we will be using np. Just type in np in terminal and it let’s you release the next version in an interactive manner. For example, this is what I had to do to release [email protected]

You might have to add the --no-tests flag to avoid testing while releasing as we have’t added tests in this tutorial

np --no-2fa --no-tests

Publish a new version of linkk (current: 0.0.1)

- fix: show version  d246822
- fix: link  a430f8a

Commit Range:


? Select semver increment or specify new version patch 	0.0.2

  ✔ Prerequisite check
  ✔ Git
  ✔ Installing dependencies using Yarn
  ✔ Bumping version using Yarn
  ✔ Publishing package using Yarn
  ✔ Pushing tags
  ✔ Creating release draft on GitHub

 linkk 0.0.2 published 🎉

Once np pushes the tags, it will open a new GitHub release page with auto-generated content. You will just have to check if everything’s right and just press that green button to release it on GitHub.

Using npx

Once the package is published, we can use it with npx too! Also no configuration is required from our side.

Using with npx

What next?

Let’s see how you can continue iterating and releasing your cli app after this


Thanks for reading the article, let me know if you found this useful.

Please drop your comments below :)