native-messaging-quickjs VS nitro

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.

Nitro is a nice https webserver that you can deploy everywhere. Comparing it to express, it doesn't need weird middlewares for json, it has a simple way to support caching, a file system router, tasks and scheduled tasks that avoid quite a few shell scripts, db:migrations etc, plugins, KV storages, SQL connectors, websockets...

Vinxi is really a kind of Meta-Router / Router Manager (built on the dev-server and bundler-toolkit Vite and the http-server Nitro). Vinxi uses various routers of your choosing as a core primitive, and allows you to compose them in a centralized config so that they work together. Be it server or client routers.

Analog allows you to deploy anywhere, literally. It uses Nitro toolkit which has options for anything while working with Vite.

For additional reading, please explore the Nitro docs at: https://nitro.unjs.io

Not to be confused with https://nitro.unjs.io the server tech behind Nuxt and SolidStart

Nuxt is powered by an internal server called Nitro. You can see its manifestation in the terminal console right after you start your local dev server:

Until it support websocket, I think it is simply a no.

https://github.com/unjs/nitro/issues/678

It's 2023 and there is a web framework that "can't" handle websocket at all. (Not even just proxying and doing nothing else.) Feels like a joke to me.

Last week, my first actual contribution into a public open source project has been merged. Its actually only a small changes into Unstorage library, which is used by Nitros server engine, which in turn used by the popular NuxtJs framework. At the time, I was stuck in one of my side project which used Nuxt because Unstorage is lacking some functionalities that I need. However because Unstorage is 2 layers deep in the dependency tree, its not trivial for me to change the code there.