diff-so-fancy VS Commander.js

The diff itself is impressive, but in terms of styling I still prefer diff-so-fancy[1]. It's easier to read at a glance.

[1]: https://github.com/so-fancy/diff-so-fancy/

I don't have much hope for this being improved anytime soon in diff-so-fancy given this issue, so I'm wondering if there's something else I can use in Terminal that would allow me to have an experience like GitLab. If that's not possible and I have to rely on a desktop application, that would be acceptable too.

This is actually one that's really easy to write and remember but I hate typing and I run it all the time, so I've aliased it down to gd for git-diff. Also I use diff-so-fancy to make the output of my diffs look frickin sweet and I suggest you do the same.

I recommend a tool like diff-so-fancy with some custom colors. You will never want to go back to vanilla diffs.

I just discovered diff-so-fancy, and very nice it is too. I immediately added it to my standard git config, which is semi-automatically installed on every machine I use. However, I've not (yet) installed diff-so-fancy on all the machines I use, and for those platforms for which it's not packaged I probably won't bother installing it from source.

I recently switched to diff-so-fancy for use in the terminal with the following configuration:

As the primary author of diff-so-fancy, which is entirely Perl, I fully support this endeavor.

Instead of delta https://github.com/dandavison/delta (shown in the previous video), I've also used diff-so-fancy https://github.com/so-fancy/diff-so-fancy and I've heard difftastic is good as well https://github.com/Wilfred/difftastic Do you use one of those or something else?

diff-so-fancy - syntax highlighting for diffs, including highlighting just the part of the line that changed: diff -ru ... | diff-so-fancy | less -R

Visit the Commander.js reference.

In the previous article, I looked at a Commander to configure and accept cli options and assign it to a variable called program.

You can write a command line utility using zx or commander.js. Hit a public api, spit stuff out in the console, etc.

In your index.js you can do whatever you want, even create an interactive CLI (check commander).

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.

Commander.js is an NPM package that makes it easier to build CLI tools. You can find its documentation over here

You can also use npm package commander to make more complex command line tool with lot of options and sub commands.

commander - npm - Required. A library that lets you define the commands and their arguments, options, help, etc.

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.

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.