`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]
...How to serve hono streamSSE via nginx reverse proxy
Serving a SPA with Hono breaks on Chrome but not Firefox.

Use hono with Turborepo's JIT packages?
tsc
.
https://turborepo.com/docs/core-concepts/internal-packages#compilation-strategies
Is there still a way I can use just-in-time packages with hono?...Lazy routers?
Issue with c.req.formData() on Vercel

ERR_UNKNOWN_FILE_EXTENSION when running `bun create hono my-app`
node:internal/errors:497 ErrorCaptureStackTrace(err); ^...
hono c.set() showing error but what is wrong and also prisma error

Cannot use `c.get` in `hono-rate-limiter`
hono-rate-limiter
package to create a middleware that enforces rate limits based on which consumer is accessing the API.
Here's my implementation:
```ts
const consumerRateLimitMiddleware = rateLimiter({...Auth0 and Hono
Does anyone have any recommendations for handling RPC response errors?
parseResult
function below so I can have consistent error handling across my app, but I've been struggling with getting type generics to work on the parseResult function such that the result type is correct.
I'm kind of curious if anyone has recommendations on how to best handle using the rpc client throughout the app, or maybe I'm just over complicating things.
```ts...Route is cached. Can't clear it even after ending server.
Changing the response in the middleware breaks it
arriValidator
now to create a new middleware for the @arrirpc/schema
validator (like the zValidator, which should actually just be standard validator, but whatever)
But, when I add the created arriValidator
to the handler, the handler just doesn't return anything, even when the middleware clearly said for it to
```ts
export function arriValidator<T extends AObjectSchema>(schema: T): MiddlewareHandler {
const problemSchema = problemResponse(schema);...
Extending the Context type
@arrirpc/schema
(yes, it's a validator), so I can use it like this ```js
export const routes = new Hono()
.get("/", async (c) => {
return respondWith(c, HealthSchema, {
status: 200,...Question about CSRF
Looking for tips about best practices
honox asset caching
public, max-age=0, must-revalidate
Is there anyway to control it? I want to cache the css, js and static files forever