-
|
Is eventSource still experimental? Can we use this feature? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 10 replies
-
|
You can use it, but be aware is still experimental and its subject to changes over the time, until it goes out of experimental |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for reply! How soon we can expect this feature to be production ready? |
Beta Was this translation helpful? Give feedback.
-
|
Depends on several factors; it is not possible to give timeline for it |
Beta Was this translation helpful? Give feedback.
-
|
The expectation that it is "not" production ready is wrong. I am the main developer for this implementation. I can assure you that I was very thorough in the implementation. It is developed up to the spec. But, there can be reasons, why you would e.g. use the "eventsource" npm package. E.g. the eventsource npm package allows you set headers while instantiating the eventsource connection. Or set a specific proxy - something which is also possible with undici, but not done on eventsource level but iirc via setting a globaldispatcher. Our EventSource implementation is now released for about 6-8 weeks. So we have not enough feedback to claim that it is battletested. But this will only be possible if we see some adaption by users like you and getting some feedback. Anyhow: the npm package "eventsource" is downloaded about 20 mio times per month and basically battletested. Our EventSource implementation is just an offer. Nobody forces you to use it ;). But it is implemented by the spec, same as the npm package "eventsource". So you should be able to replace the one with the other. So if you are worried about potential bugs or security issues, you still have the fallback option. My plan is to expose EventSource as a global in node 22. Feedback is always nice. ;) |
Beta Was this translation helpful? Give feedback.
-
|
Hey Aras, Thanks for you nice explaination and a suggestion. I will definately try eventSource npm . I used undici eventsource and I obeserve that whenever I use it I had to restart the server then it able to pick up the event data. |
Beta Was this translation helpful? Give feedback.
-
|
@tushar32 that sounds like a bug? Can you pease provide a mvce? |
Beta Was this translation helpful? Give feedback.
-
|
I will get back to you. let me do couple of more tests |
Beta Was this translation helpful? Give feedback.
-
|
Hi @Uzlopak , I am using 
The issue is when I start the epxress js server it throws error initially but when I restart the nodemon (2nd sceenshot) it's starts working. |
Beta Was this translation helpful? Give feedback.
The expectation that it is "not" production ready is wrong. I am the main developer for this implementation. I can assure you that I was very thorough in the implementation. It is developed up to the spec.
But, there can be reasons, why you would e.g. use the "eventsource" npm package. E.g. the eventsource npm package allows you set headers while instantiating the eventsource connection. Or set a specific proxy - something which is also possible with undici, but not done on eventsource level but iirc via setting a globaldispatcher.
Our EventSource implementation is now released for about 6-8 weeks. So we have not enough feedback to claim that it is battletested. But this will only be poss…