Trung Dang

The reproduction could further be limited to if **validator is used inline, as first middleware**: ```ts const testApp = app .post( validator('json', () => { return { cd: 'bar', }...

It seems like when using validator as first middleware, the response handler's `Context` cannot infer the validator's `Env` and `Input` and is typed as ``, this does not happen with...

Hi @yusukebe, Sorry for the delay gap, a bit busy this week, Still can't find the root cause yet, could also be a weird TS bug, I think for now...

Hi @EmmettM, This is expected and is normal TypeScript behavior, when you explicitly type `c: Context`, it means that `c` is now an empty default `Context`. Thus it cannot access...

Yup I see, just raising an issue to see what the maintainers think about it, omitting the `declaration` prop seems good to me. Letting it use the same build config...

Hi @nomi-san, I'm not using RDP, I was/am using/testing with Chrome Remote / Sunshine / Parsec (with fallback display setting in the Host to `off`, if set to `on` it...

Hi @nomi-san, great news, issue is fixed with the binary you linked. The main major blockage that doesn't allow the software to start is gone, though, I've found some more...

> The app has GUI and requires user logged session. You can disable the startup option and put it in Task Scheduler. I will add a option to allow it...

You are able to use a custom, non-standard fetch implement with RPC type-safety by creating a simple wrapper for `hc` output similar to the [`parseResponse`](https://hono.dev/docs/guides/rpc#parsing-a-response-with-type-safety-helper) util from `hono/client`. With that...

Btw big Nuxt/unjs ecosystem fan here too, fun fact: `parseResponse` uses `fetchRP` util, which is a modified code from `ofetch`'s response processing.