hono

Summary In proxy configurations without header size limits, this can cause real impact. Proof The author should do the following, if applicable [x] Add tests [x] Run tests [x] to format the code

PR https://github.com/honojs/hono/pull/4393 improved the ability to get accurate types for specific status codes. While this is a great improvement on its own, it is causing an issue in my project. In my project, we centrally manage 4xx and 5xx errors using a customized fetch function. Our design allows individual UI components to handle only the success cases. Previously, this meant our UI components were type-safe without needing to explicitly check the response code. However, since v4.10.0 (where https://github.com/honojs/hono/pull/4393 was released), we can no longer resolve the types without checking status or ok in each UI component. As a result, we are forced to add these checks to every single API call site. This negatively affects the codebase by reducing readability (due to increased boilerplate) and increasing the bundle size. Is there a way to maintain type safety without manually checking status or code, just as we were able to do before? Any advice would be appreciated. _Originally posted by @baseballyama in https://github.com/honojs/hono/discussions/4575_