Taku Amano

@yusukebe Thank you! Hmmm, I wonder why. The style is not applied, but I have it working as follows: the DOM has been changed as intended by the original library,...

Hi @timurxyz Thanks for creating the issue! Certainly this approach may make up for the incompleteness of hono's jsx. But hopefully we can get it to work without these workarounds....

@timurxyz Thanks for confirming and commenting! I understand the situation. > shadcn. it functionally works, though it might be a styling issue in my env that it shows like:. Sorry,...

Hmmm, this is a difficult one. There is no doubt that the current behaviour is in itself a specification. However, as the documentation recommends a similar approach, this certainly appears...

Hi @yusukebe It's not exactly “super convenient,” but the ability to run on multiple runtimes with completely identical code feels Hono-like. What do you think?

Hi @yusukebe, thanks for the comment. Indeed, it would be great if JSX worked too. It seems https://github.com/h3js/srvx uses https://github.com/unjs/jiti. https://github.com/h3js/srvx/blob/main/src/cli.ts#L265

Hi @yusukebe There's no guarantee that issue #269 will be resolved, but based on our investigation so far, I believe memory is being freed when `global.gc()` is explicitly called. How...

Hi @yusukebe, thank you for the review. Yes, I don't think it's an essential fix. Ideally, we'd eliminate the memory increase caused by AbortSignal...

Hi @yusukebe, thank you for creating the pull request. As mentioned in https://github.com/honojs/node-server/issues/146#issuecomment-2027794694, I believe that caution should be exercised when referencing `x-forwarded-proto` by default at the server layer. ###...

I also think there is room for consideration as to whether standard middleware is appropriate. I believe the following points should be specified in order to determine the appropriate design....