Error not propagated for unexpected response

[Tomas2D]

The library does not throw an error when the target server sends a JSON response instead of SSE.
It silently fails, and the node process exits with status code 13.

[Tomas2D]

ping @rexxars

[rexxars]

What is the ideal way you'd want to surface/handle errors like this?

[Tomas2D]

I would either throw the error right away and let the user handle it or add a special callback like onError so that the user
can handle it or throw their own error instead.

Another approach would be to propagate such information to onMessage. See our use-case.

https://github.com/i-am-bee/bee-agent-framework/blob/main/src/internals/fetcher.ts#L74-L103

[monokizsolt]

+1

[punkpeye]

Has anyone found a way to handle this? Is patching the source code the only way now?

[hien-prio]

@rexxars Any update? Also blocked by random Node exit.