native-messaging-quickjs VS native-messaging-deno

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.

You can use a Native Messaging host to run local code controlled from the browser. See native-messaging-deno for a general purpose and extensible solution and deno-server where Deno's serveTls is dynamically started to run a local application, stream stdout from the application to the browser, then stop the local server.

I'm basically trying to do this https://github.com/guest271314/native-messaging-deno/blob/local-server-dynamic/local_server.js without the issue with deno executable increasing CPU to over 90% when streaming, and without carrying around the rest of Deno that I will not be using. Building deno requires using Rust toolchain which is over 1GB to install before we even begin building anything, which is non-trivial to do.

https://github.com/guest271314/native-messaging-deno/tree/local-server-dynamic.

Python https://github.com/guest271314/native-messaging-python, Deno https://github.com/guest271314/native-messaging-deno, Bun https://github.com/guest271314/native-messaging-bun, Node.js https://github.com/guest271314/native-messaging-nodejsNative Messaging hosts

I'll check in a few minutes. This is the source code I use that shows N GB "VSZ" https://github.com/guest271314/native-messaging-deno and the server I will be using https://github.com/guest271314/native-messaging-espeak-ng/blob/deno-server/deno_server.js.