Use React (not hono/jsx) on top of Hono

hono/jsx is the default for UI in a Hono project. Reach for React only when something that hono/jsx cannot satisfy makes it necessary — typically a React-only component library, a React-only ecosystem tool (e.g. a specific UI kit, charting library, headless component set), or a team requirement to standardize on React.

When that is the case, do not try to bridge hono/jsx to React. Rewrite the JSX in React and treat Hono as the server framework only.

When to reach for this skill

• The UI needs a React-only library that has no hono/jsx equivalent.
• You want full React SSR with hydration, not the lighter hono/jsx/dom model.
• The team has standardized on React and the Hono side is just the server.

If none of the above applies, stay on hono/jsx — it is smaller, faster to ship, and the default for this stack. See hono and (for SPA-feel apps) hono-inertia.

Stack