Quick! Switch to Hono before Meteor 3.0 gets its stable release ![:wink: :wink:](https://forums.meteor.com/images/emoji/twitter/wink.png?v=12)
I’ve looked at bits and pieces of the Meteor source code before but I’m not knowledgeable enough to know if the following suggestion is too far out there, but: would it be feasible to make Meteor compatible with both Express and then Hono, in such a way that a gradual transition could be made (rather than another big breaking change e.g. Meteor “4.0”)?
On a tangent, something I found out about Hono recently, is that it seems intentionally designed to help you adapt WinterCG compatible frameworks to whatever targets Hono supports. For example, you could (though I haven’t tried yet) make a Elysia JS app and then mount it to Hono, then use Hono in whatever environment it supports, e.g. Node JS, AWS Lambda, Bun, etc.
See the tweet (post? what do we call these things now??) from Hono’s X account for reference:
https://x.com/honojs/status/1659569347168468995?s=20
(the actual thread starts here, but the tweet above kind of captures their intent specifically)
That said, the Hono project is quite ambitious. They’ve introduced something called Hono X (not to be confused with the pre-existing Elon Musk purchase) which seems to be something like Hono Next/Nuxt, but using the Hono JSX renderer and islands architecture? Nitro (the server engine used by Nuxt, part of the unjs project) is also doing something similar, e.g. file based routing etc, just missing the UI part. There’s also Astro moving into server-side, Fresh on Deno, etc. It’s becoming a crowded space.
Alas Hono’s my favourite “post-express” mini-server-framework so far. Though I need to play around more with Elysia JS and see how I feel about that too.
Anyway, the ecosystem Meteor 3.0 is being released into is quite different to the one Meteor 2.0 was released in… No more SPAs, a lot of different attempts at Hybrid SSR, Vite galore, and multiple viable JS runtimes to target that aren’t just Node forks.