Did a dive into git history but couldn't find anything. I like this better than wrapping the browser EventSource API in http4s-dom.

@rossabaker I found some discussion on this in #619, I still need to digest it but does anything there jog your memory?

I guess it was having a decoder that produced the prehistoric equivalent of F[Stream[F, Event]] was distasteful? You probably want to Stream.eval the decoded result from this?

Or Stream.force maybe? I did notice that, and it's slightly awkward, but I can't see why it's that big a deal.

In theory we could add a special syntax for it roundabouts here:

e.g.

final def asStream[A](implicit F: MonadThrow[F], decoder: EntityDecoder[F, Stream[F, A]]): Stream[F, A] =
  Stream.force(as[Stream[F, A]])

Otherwise not really sure what we could do about it.

I thought there was a reason, but I didn't document it and don't remember it.

Well, we figured out why 😕

• Using the client to decode Server Sent Events misbehaves on both JVM and JS #6694