Hono has support for JSX client components w/ React-like hooks: https://hono.dev/docs/guides/jsx-dom
We need to determine what pattern we're going to use to integrate limited client-side functionality for human output pages, from JSX source.
For example, the current website shows a status indicator in the navigation, and that will need some client-side logic to fetch the status page endpoint and set a JSX state.
HonoX (https://github.com/honojs/honox) is a potential option as it has built-in support for "Islands" that are client components, however, it is designed as a meta-framework and so would force us into a specific source code structure.
Ideally, I'd like to stick to the current code structure where this worker is just a regular old worker, and so any human output that we generate should be self-contained to that response (inline scripts for any client component hydration, rather than needing to build + bundle scripts to be served in advance).
Hono has support for JSX client components w/ React-like hooks: https://hono.dev/docs/guides/jsx-dom
We need to determine what pattern we're going to use to integrate limited client-side functionality for human output pages, from JSX source.
For example, the current website shows a status indicator in the navigation, and that will need some client-side logic to fetch the status page endpoint and set a JSX state.
HonoX (https://github.com/honojs/honox) is a potential option as it has built-in support for "Islands" that are client components, however, it is designed as a meta-framework and so would force us into a specific source code structure.
Ideally, I'd like to stick to the current code structure where this worker is just a regular old worker, and so any human output that we generate should be self-contained to that response (inline scripts for any client component hydration, rather than needing to build + bundle scripts to be served in advance).