How to handle aborted request / Browser reload while sending a stream ?

[geminigeek]

hi,
i am sending data like this in a test setup , its working fine, the browser is getting data, but if i reload the browser while data is streaming, i get error check below, how to catch/handle it ?

app.get("/events", (request, response) => {
  let i = 0
  const s = setInterval(() => {
    i++
    console.log("sending event", i)
    response.write(JSON.stringify({ value: "test value", val: i }))
  }, 1000)

  setTimeout(() => {
    clearInterval(s)
    response.end()
  }, 10000)
})

error i am getting

node:events:492
      throw er; // Unhandled 'error' event
      ^

Error: uWS.HttpResponse must not be accessed after uWS.HttpResponse.onAborted callback, or after a successful response. See documentation for uWS.HttpResponse and consult the user manual.
    at <redacted>\node_modules\hyper-express\src\components\http\Response.js:584:32
    at new Promise (<anonymous>)
    at Response._stream_chunk (<redacted>\node_modules\hyper-express\src\components\http\Response.js:583:16)
    at Response._write (<redacted>\node_modules\hyper-express\src\components\http\Response.js:443:18)
    at writeOrBuffer (node:internal/streams/writable:556:12)
    at _write (node:internal/streams/writable:490:10)
    at Writable.write (node:internal/streams/writable:494:10)
    at Response.passthrough [as write] (<redacted>\node_modules\hyper-express\src\components\http\Response.js:959:29)
    at Timeout._onTimeout (<redacted>ServerHye.mjs:162:19)
    at listOnTimeout (node:internal/timers:573:17)
Emitted 'error' event on Writable instance at:
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

[kartikk221]

Refer to https://github.com/kartikk221/hyper-express/blob/master/docs/Request.md#request-events
You may listen for the abort or closed event both of which will indicate no Response write operations can be performed going forward.

[kartikk221]

Also, If you are sending events like you are, look into using the Response.sse API which lets you do Server Sent Events with HyperExpress.

[geminigeek]

hi,

thanks for your reply i will surely look into "Response.sse" , i am just evaluating my test cases as i am looking to port an existing api to hyper express ,

secondly the latest update of hyper express the issue i was facing is not happening , it seems you have fixed the issue , thanks