hono VS nitro

I used hono to implement worker.

Hono - Ultrafast web framework for the Edges

Hono is an ultrafast web framework for the edge and it's amazing. It's simple as express and the DX is mind-blowing. And now you can also serve JSX with it 🤯. Anyone in the industry for long enough knows that a setup like this can be quite tedious to manage and maintain. I might sound biased for Hono, and that's true, I love it ❤️.

Please could a fellow HNer who has experience using this explain in simple terms what Hono on a Cloudflare Worker enables that one cannot already do with a vanilla worker?

The docs[0] are not instructive on this point.

[0] https://hono.dev

Hono, a powerful framework, is our secret sauce for crafting high-performance APIs. With its intuitive syntax and seamless integration with Next.js, Hono simplifies the process of optimizing API performance.

Hono—a simple and fast framework for processing HTTP requests.

A good alternative of this can be - [Hono]https://hono.dev/

I agree that “fast, lightweight, web standards” isn’t much of a description but not too far down https://github.com/honojs/hono I did this:

> Hono … is a small, simple, and ultrafast web framework for the Edges. It works on any JavaScript runtime: Cloudflare Workers, Fastly Compute, Deno, Bun, Vercel, AWS Lambda, Lambda@Edge, and Node.js.

Hono offers good DX and a blazingly fast library to help you build your backend with native RPC embedded in its code. It has Zod support and it's written with TypeScript with very readable types so you can understand what's happening. It also supports Bun and a bunch of runtimes so you can run it everywhere. Check the documentation! It's also very helpful.

Initialize your hono project using bun:

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.