native-messaging-quickjs VS Commander.js

QuickJS https://github.com/guest271314/native-messaging-quickjs (after strip the executable is less than 1MB; the last time I checked node executable is well over 80MB) to run ImageMagick and pipe the result to local file system, remote end-point, or to the browser as a stream.

Dynamically set arbitrary Web pages as "externally_connectable" and forward messages from the Web page to Native Messaging host the forward messages from Native Messagin host back to arbitrary Web page https://github.com/guest271314/native-messaging-quickjs/tree/dynamic-externally-connectable

I can ship qjs in a browser extension with no undue constraint on storage, and run qjs from the browser from any Web site https://github.com/guest271314/native-messaging-quickjs/tree/dynamic-externally-connectable. That is a different story for node and deno, when we really analyze the built-ins we use, do not amount to all of the built-ins, however, there is no way that I am aware of to reduce the size of V8 engine; even d8 is what, 20MB, and not simple to extend to actually use stdin, stdout.

Working JavaScript (QuickJS) version: https://github.com/guest271314/native-messaging-quickjs/blob/main/nm_qjs.js

A QuickJS Native Messaging host that echoes input https://github.com/guest271314/native-messaaging-quickjs from client. Have fun.

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.