Q: why does utils/stream.ts/write() fail silently by default?

[georgernstgraf]

Hey, I am doing an app with hono on node. see repo.

There is a long-running database job and I want to get updates from it pushed into the gui using sse's. Basically I got it doing what I need here, but I wanna know how it is meant by hono.

hono's stream.ts in write() has an empty catch {} here .. and when I insert a throw() here, everythings works great for me,
writing to the closed stream throws and I can cleanup properly.

Your comments states sth. like "write you own stream if you wanna catch". ok.

The hono website recommends this:

app.get('/sse', async (c) => {
  return streamSSE(c, async (stream) => { .... }

But doing this, there is no option to change the stream.

• Basically I'd like a throw in hono's stream.
• But I can work around by asking the stream if it is open, right?
• I'd love to understand your rationale behind this empty catch.

Thank you so much! -- George

[georgernstgraf]

Okay, I think I get it:

I should trust the streams onAbort() and make this a condition to return from the sse handler/endpoint.

My updated code is here .

Please close this discussion if you consider this correct ;-)

thanks again!