qjs-ws VS native-messaging-nodejs

Interestingly I just built https://github.com/ratboy666/qjs-ws yesterday. QuickJS qjs executable stripped is less than 1MB. node executable is over 80MB.

And/or control node and any other programming language from the browser using Native Messaging native-messaging-nodejs.

We can process asynchronous tasks without blocking reading stdin (e.g., full-duplex).

WHat do you mean by "contribute"? I download only the node executable using download-node-nightly-executable to run native-messaging-nodejs, servers, or whatever else I decide to experiement on - without downloading any packages.

I re-wrote the original code substituting using readSync for process.stdin.on('readable', () => {}) and including process.stdout._handle.setBlocking(true) and readFullSync function contributed by a Deno user https://github.com/guest271314/native-messaging-nodejs/blob/main/nm_nodejs.mjs. I wanted to a) get the input message (up to 1MB at a time) echo'ed back to the client; and b) get away from using process.stdin.on('readable', () => {}), rather use an approach that did not include event listeners; c) get away from using CommonJS and package.json and instead use Ecmascript modules without package.json.

If you want you can use a Node.js Native Messaging host https://github.com/guest271314/native-messaging-nodejs, Deno, QuickJS, txiki.js, Bun, C, C++, Python, WASI/WebAssembly or whatever language is built in, e.g., Bash.

I just fetch the nightly node executable, get rid of everything else in the archive, use .mjs extension for import to work without package.json, then I can connect to the host https://github.com/guest271314/native-messaging-nodejs, and start subprocesses, e.g., raw PCM streams, where stdout is streamed to the client (browser), e.g, https://github.com/guest271314/captureSystemAudio/blob/master/native_messaging/capture_system_audio/capture_system_audio_node.js.

Yes, utilizing Native Messaging https://github.com/guest271314/native-messaging-nodejs.