fetch-event-source
fetch-event-source copied to clipboard
Azure
A better API for making Event Source requests, with all the features of fetch()
Hello, these changes (somehow similar to https://github.com/Azure/fetch-event-source/pull/8) are the minimal ones I had to do to get FetchEventSource working in a web worker context. I've also added some unit tests...
The retry mechanism did not abort the original fetch which can lead to many open connections.
Amazing package! Just wanted to check if there could be a way to also support this in non-browser node.js environments. I was able to get this working in node for...
Hello! While I was working with server-sent events I've discovered similar shortcomings as you. Glad your library exists to fix them! One issue I've discovered with your library is that...
an error is seen in the browser tools using the below call `TypeError: Error in body stream` ```javascript await new fetchEventSource( `${endpointUrl}/path-does-not-exist`, { onerror ( err ) { console.log( 'error',...
As per the current implementation, whenever the page visibility changes the connection will be disconnected & then reconnect only after the page comes back to visibility (during the time of...
## Description The sourcemaps in the published package reference files that are not included in the published package. When I use this package in my create-react-app project, I see the...
With this change fetchEventSource can be used from within a web worker
The `onmessage` callback is called with an empty message if the server sends `\n:\n`. The spec says that servers can choose to send `:` as a form of keep-alive message...
eg, change this ```javascript export { fetchEventSource, EventStreamContentType } from './fetch'; ``` to this ```javascript export { fetchEventSource, EventStreamContentType } from './fetch.js'; ``` this change would make the script sources...