Viktor

@ljharb thanks, now it is better!

@ljharb , hm... I have deleted the minified version for simplicity, thanks

@ljharb , but 1.0.29 has no the malware in the obfuscated code, unless it is so much hidden so I cannot see it. I am not hiding it, the npm...

please update the eventsource-polyfill, thanks

@MmtBkn , hello, it is very strange, could you check if polyfill is used instead of native EventSource and why?

@verbeeckjan, polyfill uses the fetch api, so you should see it on the XHR subtab. Please look

@larsnedb , isn't this a bug in Chrome DevTools ? Do you have a linked to the issue in the DevTools?

Can you prevent the error logging for narive EventSource?

@roman-sereda-lohika why was it working fine? I think, before some version, the error was not thrown or reported for this case. in other place of the code I was using...

if you want to ignore the errors, some mechanism is needed. I can think of an 1) extra option or 2) event.preventDefault(); and checking if preventDefault was called in the...