Roadmap to v2.0.0

Now, Hono has become a great framework. It has much built-in middleware, fine DX, flexible routings, and high-performance routers. Then, the basic API design is fixed. But I think we have a lot of things to do with Hono yet.

We can support Deno and Bun. It’s still just experimental. We can make it complete.

How about making third-party middleware. The coupling of firebase-auth-cloudflare-workers seems good. Organizing current middleware, I’m planning separate the middleware that does not depend on other libraries and middleware that depends on other libraries such as graphql-server or mustache. To make it clean, how about making the github.com/honojs/graphql-server repository, and moving current code into that. Additionally, how about using @honojs/graphql-server namespace in the npm repository. I’ve already got the honojs org in npm repo.

And, I want to make validator middleware. That is what I want.

In this way, we have many things to do. So, I decided to implement almost things and release them as v2.0.0. Is it good? Listed what I want to do roughly below. If you have a feature request. Please write it in the comments.

---

• Support Deno #351
• Test well on Deno #351
• CI for Deno #364
• Support Bun #344
• serve-static middleware for Bun
• Test on Bun
• Make repository for middleware using third party libraries #350
• Move the middleware using third party libs in current repository to new repository later #350
• Use honojs org on npm repository later #350
• Make @honojs/xxx namespace later #350
• github.com/honojs/xxx repository later #350
• Make validator middleware as builtin later
• firebase-auth middleware as third party later
• prometheus middleware as third party later #263
• Remove graphql-server middleware from this repo #357
• Remove mustache middleware from this repo #354
• Access privileges for github repo later
• Access privileges for npm repos later
• Make body-parse into Context? #362
• Make cookie into Request/Reponse #353
• Integrate app.fetch and app.request?
• New middleware structure #350
• Documenation
• Website
• Migration guide
• And, others

By the way, we don’t have to implement all things.

[yusukebe]

Hi @Code-Hex !

I think this is an good example to manage way some middlewares to npm registry.

Thanks for sharing!

@Code-Hex @metrue, I’ve written my thought about the middleware structure: #350 Check it out.

[yusukebe]

Hi @metrue !

Are you talking about the graphql schema validation?

No, I want to validate Request body or query parameters. For example, “express-validator” is similar to what I want to do. https://express-validator.github.io/docs/

Like “express-validator”, user can use validator.js. I think it’s OK to use this library if user wants to validate it perfectly. But, I want to have more tiny validator for casual use. It will be built-in middleware.

Although, I don’t have a plan for validation syntax, API design, and, interface. We’ll consider how we make it.