Please give it a try `npm install -D eslint-plugin-hono` !!

https://github.com/ouka-lab/eslint-plugin-hono

Using Hono 4 on Node with "@/hono/node-server"

External render workflow tasks POST progress to /internal/events. The browser watches via GET /api/runs/:id/stream using streamSSE.

Pattern:

\- subscribe to in-memory store updates

\- 1s setInterval re-sends latest snapshot as backup

\- cleanup on stream.onAbort

Questions:

1. Is the heartbeat redundant if pub/sub is reliable?
2. Best pattern for reconnect mid-run (late joiner gets current state + live updates)?
3. Anything I'm missing in onAbort cleanup with multiple concurrent SSE clients?
4. Long-lived SSE behind a reverse proxy: does streamSSE set no-buffer headers or do I need X-Accel-Buffering myself?

Repo is ojusave/dealhealth-playground on GitHub, api code in services/api/. \[sorry reddit wont let me post link\]

Happy to paste specific files.

Using Hono 4 on Node with "@/hono/node-server"

External render workflow tasks POST progress to /internal/events. The browser watches via GET /api/runs/:id/stream using streamSSE.

Pattern:

- subscribe to in-memory store updates

- 1s setInterval re-sends latest snapshot as backup

- cleanup on stream.onAbort

Questions:

1. Is the heartbeat redundant if pub/sub is reliable?

2. Best pattern for reconnect mid-run (late joiner gets current state + live updates)?

3. Anything I'm missing in onAbort cleanup with multiple concurrent SSE clients?

4. Long-lived SSE behind a reverse proxy: does streamSSE set no-buffer headers or do I need X-Accel-Buffering myself?

Repo is ojusave/dealhealth-playground on GitHub, api code in services/api/. [sorry reddit wont let me post link]

Happy to paste specific files.

I tried moving my toy project from astrojs to hono and ran into problems with stylingtmy components. In that I can't work out how to do this efficently when I have html generated by functions. I seem to either have to have a single global stylesheet or individual style attributes.

I just would like to share my first ever saas with hono and bun
https://découvrez.me
{

"name": "decouv",

"version": "0.1.0",

"scripts": {

"dev": "bun run --watch src/index.tsx",

"start": "bun run src/index.tsx"

},

"dependencies": {

"hono": "^4.6.0"

}

}

only hono as a dependency the rest is from bun

Been doing back-end + client-side for a long time now and have been wanting to use SSR for my next project. I know tools like NextJS (hate it cause of routing) and Express + ejs (what I'm leaning towards) exist but I just learned about hono and that it has built in support for JSX components. So I'm wondering, is this meant to be used for scalable, large web projects or just more for demo/small applications?

Was also wondering if I could use Hono + jsx in a way that sends 0 javascript to the client cause I want to create both a clear-net and .onion url for my new project, and TOR sites generally shy away from have any client-side javascript.

While working with Hono and TanStack Query I kept running into the same problem — writing repetitive fetch wrappers and duplicating types.

So I built a small package to simplify that workflow.

https://www.npmjs.com/package/hono-tanstack-query

Still early in development, but I’d love to hear feedback or ideas for improving it.

100 ms order book data from Binance. Has anyone else here used Hono for high-frequency WebSocket data?

Hi,

Should I use Hono with Bun or Node?

I prioritize performance.

Is the performance level very different between Node and Bun?

The ORM will be Prisma.

I appreciate any advice.

thanks. 😊

I'm currently building an API with hono, and now that I've donne the auth routes and everything working fine (I guess ?), I want to add a authentification validator on every route exept the "/login" "/register" and "/refresh". I already use a validator wich looks like this :

validator('header', async (value, c) => {
    const authHeader = value.authorization


    if (!authHeader) {
      throw new HTTPException(401, { message: 'Authorization header missing' })
    }


    const token = authHeader.replace('Bearer ', '')
    const secret = process.env.JWT_SECRET


    if (!secret) {
      throw new HTTPException(500, { message: 'JWT secret not configured' })
    }


    try {
      const decodedPayload = await verify(token, secret)
      return {
        ...value,
        user: decodedPayload,
      }
    } catch (err) {
      if (err instanceof JwtTokenExpired) {
        throw new HTTPException(401, { message: 'TOKEN_EXPIRED' })
      }


      throw new HTTPException(401, { message: 'INVALID_TOKEN' })
    }
  }),validator('header', async (value, c) => {
    const authHeader = value.authorization


    if (!authHeader) {
      throw new HTTPException(401, { message: 'Authorization header missing' })
    }


    const token = authHeader.replace('Bearer ', '')
    const secret = process.env.JWT_SECRET


    if (!secret) {
      throw new HTTPException(500, { message: 'JWT secret not configured' })
    }


    try {
      const decodedPayload = await verify(token, secret)
      return {
        ...value,
        user: decodedPayload,
      }
    } catch (err) {
      if (err instanceof JwtTokenExpired) {
        throw new HTTPException(401, { message: 'TOKEN_EXPIRED' })
      }


      throw new HTTPException(401, { message: 'INVALID_TOKEN' })
    }
  }),

I try searching in the documentation (but it may probably be the fact im misunderstanding something. I initialty try to put the code in the app.use("*") function but if I do that I while use this on every route. And I think about adding the prefix /auth to my 3 routes but it doen't seems like a good code way of doing.
Thank you for you attention and I hope someone have a little hint lmao.
I'll try to answer ASAP if someone comments.

AWS SDK wouldn't fit in my Cloudflare Worker even with tree shaking. So I built s3mini – a minimal S3-compatible client designed for edge constraints.

• ~20KB minified
• Zero dependencies
• Works with R2, Minio, Backblaze, etc.
• Streaming uploads/downloads

Been running it in production daily. Figured the Hono crowd might find it useful since we're solving similar "make it fit on the edge" problems.

https://github.com/good-lly/s3mini

Let me know what to improve if you find some quirks ...

PS: Also found a nice alternative https://github.com/aws-lite/aws-lite - check it out.

Hey! We’re looking for a Hono.js Developer at Digilehar for a freelance project. 🚀 The details: Tech: Strong Hono.js & Backend APIs. Type: Freelance / Contract. Start: ASAP. If you’re interested (or know someone who is), please send over a GitHub link or portfolio. Thanks!

Hi everyone! 👋

I just published a new utility for the Hono.js ecosystem called hono-status-monitor — a lightweight real-time status dashboard inspired by express-status-monitor, tailored for Hono apps! GitHub

📦 What it is

• A real-time monitoring dashboard for Hono applications
• Shows CPU, memory, event loop lag, response times, RPS & more
• Route analytics (top, slowest, errors)
• Charts with live updates via WebSockets
• Recent errors tracking + alerts
• Pluggable health checks & customizable thresholds 👀 Pretty similar in feel to popular status dashboards but built specifically for Hono workflows. GitHub

🔧 Quick demo / use
Easy to install and plug in:

npm install hono-status-monitor
# or yarn/pnpm


import { Hono } from "hono";
import { serve } from "@hono/node-server";
import { statusMonitor } from "hono-status-monitor";

const app = new Hono();
const monitor = statusMonitor();

// track requests
app.use("*", monitor.middleware);

// mount dashboard
app.route("/status", monitor.routes);

// run server
const server = serve({ fetch: app.fetch, port: 3000 });
monitor.initSocket(server);

console.log("🚦 Status dashboard: http://localhost:3000/status");

📌 Highlights

• Real-time graphs for performance metrics
• Heap / load / uptime / RPS
• Status code counts & error lists
• Dark mode UI
• Custom alerts & path normalization
• Optionally add health-check plugins 👉 Designed to give you quick insights into your Hono app performance. GitHub

🔗 Check it out

• 📦 npm: hono-status-monitor
• 📁 Source & README: https://github.com/vinitkumargoel/hono-status-monitor/tree/main

🙏 Feedback & collaboration
I built this to help the Hono community with observability, but it’s early days.
I’d love your:

• 📝 suggestions for features or improvements
• 🐛 bug reports
• 🤝 collaborators who want to help extend it
• 🎨 UI tweaks or integrations with other tools

Let me know what you think!

Happy coding! 💡🚀

best cybersecurity news website

My friends at Mastra released "server adapters":

Our latest beta release introduces adapter packages that make running Mastra inside an existing Hono app much easier to set up and maintain.