native-messaging-bash VS native-messaging-quickjs

I use a Bash start up script every few days when the experiments I run wind up freezing tip-of-tree Chromium or Nightly or the OS itself. The script fetches lastest Firefox Nightly, Chromium Dev Channel installs libtool, libcurl4-openssl-dev, texinfo, cmake, bleachbit, espeak-ng, python3-speechd mpv, git, libssl-dev, clang (or build-essential). I use git frequently. I also wrote a Bash Native Messaging host to communicate from the browser to the local shell script that is W.I.P. https://github.com/guest271314/native-messaging-bash.

Here is a Native Messaging host written in Bash https://github.com/guest271314/native-messaging-bash that you can write stdin to and get stdout from in the browser.

This is how you install and test Native Messaging host, substitute Bash script https://github.com/guest271314/native-messaging-bash and names for for Node.js host https://github.com/guest271314/native-messaging-nodejs.

Bash: https://github.com/guest271314/native-messaging-bash/blob/main/nm_bash.sh

No folders need to be edited. It is not necessary to download a binary. A Native Messaging host using Bash https://github.com/guest271314/native-messaging-bash; I also wrote Native Messaging hosts in C, C++, and QuickJS https://github.com/GoogleChrome/developer.chrome.com/issues/3718#issuecomment-1250341188; others have written Native Messaging hosts in PHP, Python, etc. You should be able to use C# or whatever is the shell on *indows to achieve the same result.

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.