Yusuke Wada

I think it's enough to use `app.route`, so we don't implement `fromLookup`. ```ts const app = new Hono() const routes = app.route('/', a).route('/', b).route('/', c) ``` If you don't want...

@harrysolovay Thank you for the explanation. I'm not sure this feature you said is what many users want. So, I leave this issue, and if someone needs this, please add...

Hey. There are some ways to get environment variables: 1. Getting from `c.env` by passing the variables to `devServer.env` as [@dihmeetree mentioned](https://github.com/honojs/vite-plugins/issues/258#issuecomment-2870063127). 2. Using Vite specific functions as [@ilmeskio mentioned](https://github.com/honojs/vite-plugins/issues/258#issuecomment-2875598036)...

@Soviut I see. By the way, are you using an adapter like `@hono/vite-dev-server/cloudflare`?

I think this is just difficult to use, but it's expected behavior. We have to get the variables that are set with a `VITE_` prefix in `.env` and `.env.local` files...

Hi @marceloverdijk I have some ideas for treating constants. I'll share them later.

Hi @BryanAbate It's useful that it infers as `number`, but the following code will throw `400`. ```ts const app = new Hono() const routes = app.get( '/', zValidator( 'query', z.object({...

My opinion is not changed. It's written on my comment: https://github.com/honojs/hono/issues/3495#issuecomment-2398059177.

@isnifer I think it works well now: ```ts const schema = z.object({ someEnum: z.enum(['PLEASE', 'READ', 'A', 'SCHEMA']) }) const app = new Hono().get('/', zValidator('query', schema), (c) => { const q...

@isnifer That is related to https://github.com/honojs/middleware/issues/1370