Fresh 2 is changing to an API design, similar to frameworks like Express and Hono.
In Fresh 1, the community and developers were free to develop middleware and plug-ins.
In the case of Hono, the availability of a variety of official middleware is considered one of the reasons for its popularity.
Why don't you introduce official middleware to Fresh, too?
At first, I think porting some of the middleware available in Hono would be a good starting point.
basic, CSRF, cache, CORS ex.
The repository for managing them doesn't necessarily have to be part of the main Fresh repository.
For example, denoland/fresh-extensions.
I would be willing to dedicate my efforts to porting middleware if the community, including myself, shares the same understanding.
Would providing official middleware go against Fresh's philosophy or policy?
I would really appreciate hearing thoughts on this.
Fresh 2 is changing to an API design, similar to frameworks like Express and Hono.
In Fresh 1, the community and developers were free to develop middleware and plug-ins.
In the case of Hono, the availability of a variety of official middleware is considered one of the reasons for its popularity.
Why don't you introduce official middleware to Fresh, too?
At first, I think porting some of the middleware available in Hono would be a good starting point.
basic, CSRF, cache, CORS ex.
The repository for managing them doesn't necessarily have to be part of the main Fresh repository.
For example, denoland/fresh-extensions.
I would be willing to dedicate my efforts to porting middleware if the community, including myself, shares the same understanding.
Would providing official middleware go against Fresh's philosophy or policy?
I would really appreciate hearing thoughts on this.