nitro VS vue-loader

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.

doesn't have the problematic leak behavior.

I am would like to have the added benefits of the encapsulated ShadowDOM on a Custom element, but would also like the versatility of keeping my SFCs as SFCs so that I can use them and any content placed in their slots as I normally would, without having to take the added encapsulation of the Shadow DOM into consideration if possible. Another developer had previously mentioned wanting an easy way to import styles from a SFC into a Custom element in this post, and Evan You replied that it is possible, but I was unable to find an example of it being done.

I am not proud of this solution, but it should only be necessary until a PR is accepted with these changes: