Taku Amano
Taku Amano
What about a feature like this, which would greatly expand the possibilities of JSX? ### What can we do? The following example shows the writing of a style element using...
fixes #1953 ### Tidy up Suppress errors from `yarn lint:fix` * 2c521b2b771bacbba6b90072b52c7cc0849714fe * 57cef10b0dee45a40b75e7fde8a0bd097bd23976 ### Tweaks vitest.config.ts Exclude "\*.case.test.ts" from vitest These special files are used to share test cases...
### What is the feature you are proposing? Currently, if Content-Type is not found, it is processed as text/plain, resulting in a .txt file name. https://github.com/usualoma/hono/blob/dcb740176f8e4e26783bac05ba5bd6ea7ef4e09d/src/helper/ssg/index.ts#L164 I wonder if there...
fixes #2517 ### Author should do the followings, if applicable - [x] Add tests - [x] Run tests - [x] `yarn denoify` to generate files for Deno
There was a bug where the hook state was not maintained when passed as `children`. This is not a specification change, but a fix to the original expected behaviour, so...
#2508 ### What is this? Improve compatibility with React and make the Getting started level code work for the following UI components * [react-toastify](https://github.com/fkhadra/react-toastify) * [spinners-react](https://github.com/adexin/spinners-react) * [Radix UI Primitives](https://www.radix-ui.com/primitives)...
### What is this? * When island components are nested, the outermost components are wrapped in `honox-island` and the inner components are not. * However, in template elements for restoring...
https://github.com/honojs/honox/issues/157 It is more effective when used together with https://github.com/honojs/hono/pull/2577
fixes #156 Use the `component-export` mentioned in isseu to wrap an export matching the following name as an island component. https://github.com/honojs/honox/compare/main...usualoma:honox:feat/export-named-component?expand=1#diff-dbf4bfe9bdc2ab09701d7f99d62aa69e45740919b350c8166aebe64daa3fdd54R39-R41
In #56 we can now pass child components to children. The documentation for next.js stated the following. > You're not limited to the children prop. you can use any prop...