Hono and cloudflare bindings
hono + vercel + monorepo + turborepo -- what is the trick?
Unable to render jsx with bun
error: Cannot find module 'react/jsx-dev-runtime'
.
Sample code:
```ts
import {Hono} from 'hono'...Can I use JavaScript?

Serve Static file fail

OpenAPI route with 204 + content: {} cause type error with c.body(null, 204)
@hono/zod-openapi 0.18.4 @hono/zod-validator 0.4.3...
How to middleware to recursive fetches (ESI subrequests)
Hono: getCookie() Returns Undefined — Need Help!

OpenAPI not validating content type?
double encoding oauth redirect uri
redirect_uri=https%253A%252F%252F...
❌
- Local: redirect_uri=https%3A%2F%2F...
✅
Setup:...How to Retrieve Session in Next.js RSC Without Getting 401 (Next.js + Hono Integration)
Type Error with zodValidator and arktypeValidator
Getting corrupted binary responses instead of JSON from Hono gateway service with axios
React Native / Expo

Inferring the response type of a handler
JSX with no-value attribute
<input data-bind-foo />
or <div data-signals-bar></div>
. But Hono converts them to <input data-bind-foo="true" />
and <div data-signals-bar="true"></div>
, causing datastar error.
Is it possible to turn off that feature without using raw()?
...`args?` is blank despite using zValidator
How to Achieve Full Type-Safe Communication Between a Hono Server and a Next.js Client in a Monorepo
Discriminated Unions from AppType
hc<typeof app>
. I have an API route that returns 400
and { success: false, error: SomeTypes }
. Generally I would expect this to create a discriminated union on result.ok
or on body.success
(or both!) but neither seems to work.
This seems to be related to returning c.json()
multiple times in my route, but in theory I would expect this to consolidate types.
I've attached some screenshots as an example. In the last screenshot instead of success: boolean
it should be a literal, success: false
which would allow me to use it as a discriminate. Would love any insight folks have!...
HTTP Status bug
post
request.
Previous get
requests return data correctly, but this one is giving me problems for some obscure reason.
This results in an Internal server error
Error message:
The status provided (0) must be 101 or in the range of [200, 599]
...