hono

Really love the ideas behind Deno, and tried to do things the Deno way (Deno.json, JSR, modern imports, Deno Deploy) for a monorepo project with Next.js, Hono and private packages. Some things like Hono worked super well, but Next.js did not. Other things like types would sometimes break in subtle ways. The choice of deployment destination e.g. Vercel for Next also gave me issues. Here is an example of a small microcut I faced (which might be fixed now) https://github.com/honojs/hono/issues/1216 In contrast, Bun had less cognitive overhead and just "worked" even though it didn't feel as clean as Deno. Some things aren't perfect with Bun either like the lack of a Bun runtime on Vercel

Yeah being subjetive is fine. We all have tastes and preferences and that's why there are so many frameworks and ecosystems. Going to nitpick a little here Hono docs language says, they wrap the standard Request object that you can access via HonoRequest.raw https://github.com/honojs/hono/blob/main/src/request.ts#L26 Annotations/Decorators are in stage3 of JavaScript. But I agree they are not super common in JS world except TS heavy libs or frameworks. Btw we aren't big fan of them and use them sparsely in models and commands only

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 find 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.

No - please check out Hono https://github.com/honojs/hono